fkie_cve-2024-42126
Vulnerability from fkie_nvd
Published
2024-07-30 08:15
Modified
2024-11-21 09:33
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: powerpc: Avoid nmi_enter/nmi_exit in real mode interrupt. nmi_enter()/nmi_exit() touches per cpu variables which can lead to kernel crash when invoked during real mode interrupt handling (e.g. early HMI/MCE interrupt handler) if percpu allocation comes from vmalloc area. Early HMI/MCE handlers are called through DEFINE_INTERRUPT_HANDLER_NMI() wrapper which invokes nmi_enter/nmi_exit calls. We don't see any issue when percpu allocation is from the embedded first chunk. However with CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK enabled there are chances where percpu allocation can come from the vmalloc area. With kernel command line "percpu_alloc=page" we can force percpu allocation to come from vmalloc area and can see kernel crash in machine_check_early: [ 1.215714] NIP [c000000000e49eb4] rcu_nmi_enter+0x24/0x110 [ 1.215717] LR [c0000000000461a0] machine_check_early+0xf0/0x2c0 [ 1.215719] --- interrupt: 200 [ 1.215720] [c000000fffd73180] [0000000000000000] 0x0 (unreliable) [ 1.215722] [c000000fffd731b0] [0000000000000000] 0x0 [ 1.215724] [c000000fffd73210] [c000000000008364] machine_check_early_common+0x134/0x1f8 Fix this by avoiding use of nmi_enter()/nmi_exit() in real mode if percpu first chunk is not embedded.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/0db880fc865ffb522141ced4bfa66c12ab1fbb70
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/0f37946c62c48a907625348cbc720a7a0c547d1e
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/2c78c9411e685dbc9eac8c2845111b03501975b8
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/8d3f83dfb23674540c827a8d65fba20aa300b252
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/e2afb26615adf6c3ceaaa7732aa839bcd587a057
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/fb6675db04c4b79883373edc578d5df7bbc84848
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/0db880fc865ffb522141ced4bfa66c12ab1fbb70
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/0f37946c62c48a907625348cbc720a7a0c547d1e
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/2c78c9411e685dbc9eac8c2845111b03501975b8
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/8d3f83dfb23674540c827a8d65fba20aa300b252
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "In the Linux kernel, the following vulnerability has been resolved:\n\npowerpc: Avoid nmi_enter/nmi_exit in real mode interrupt.\n\nnmi_enter()/nmi_exit() touches per cpu variables which can lead to kernel\ncrash when invoked during real mode interrupt handling (e.g. early HMI/MCE\ninterrupt handler) if percpu allocation comes from vmalloc area.\n\nEarly HMI/MCE handlers are called through DEFINE_INTERRUPT_HANDLER_NMI()\nwrapper which invokes nmi_enter/nmi_exit calls. We don't see any issue when\npercpu allocation is from the embedded first chunk. However with\nCONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK enabled there are chances where percpu\nallocation can come from the vmalloc area.\n\nWith kernel command line \"percpu_alloc=page\" we can force percpu allocation\nto come from vmalloc area and can see kernel crash in machine_check_early:\n\n[    1.215714] NIP [c000000000e49eb4] rcu_nmi_enter+0x24/0x110\n[    1.215717] LR [c0000000000461a0] machine_check_early+0xf0/0x2c0\n[    1.215719] --- interrupt: 200\n[    1.215720] [c000000fffd73180] [0000000000000000] 0x0 (unreliable)\n[    1.215722] [c000000fffd731b0] [0000000000000000] 0x0\n[    1.215724] [c000000fffd73210] [c000000000008364] machine_check_early_common+0x134/0x1f8\n\nFix this by avoiding use of nmi_enter()/nmi_exit() in real mode if percpu\nfirst chunk is not embedded.",
      },
      {
         lang: "es",
         value: "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: powerpc: Evite nmi_enter/nmi_exit en interrupción en modo real. nmi_enter()/nmi_exit() toca variables por CPU que pueden provocar un fallo del kernel cuando se invoca durante el manejo de interrupciones en modo real (por ejemplo, el controlador de interrupciones HMI/MCE temprano) si la asignación de percpu proviene del área vmalloc. Los primeros controladores HMI/MCE se llaman a través del contenedor DEFINE_INTERRUPT_HANDLER_NMI() que invoca llamadas nmi_enter/nmi_exit. No vemos ningún problema cuando la asignación de percpu proviene del primer fragmento integrado. Sin embargo, con CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK habilitado, hay posibilidades de que la asignación de percpu pueda provenir del área vmalloc. Con la línea de comando del kernel \"percpu_alloc=page\" podemos forzar que la asignación de percpu provenga del área vmalloc y podemos ver el fallo del kernel en machine_check_early: [1.215714] NIP [c000000000e49eb4] rcu_nmi_enter+0x24/0x110 [1.215717] LR [c0000000000461a0] check_early+0xf0/ 0x2c0 [1.215719] --- interrupción: 200 [ 1.215720] [c000000fffd73180] [0000000000000000] 0x0 (no confiable) [ 1.215722] [c000000fffd731b0] 000] 0x0 [ 1.215724] [c000000fffd73210] [c000000000008364] machine_check_early_common+0x134/0x1f8 Solucionar esto mediante evitando el uso de nmi_enter()/nmi_exit() en modo real si el primer fragmento de percpu no está incrustado.",
      },
   ],
   id: "CVE-2024-42126",
   lastModified: "2024-11-21T09:33:39.437",
   metrics: {},
   published: "2024-07-30T08:15:04.743",
   references: [
      {
         source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
         url: "https://git.kernel.org/stable/c/0db880fc865ffb522141ced4bfa66c12ab1fbb70",
      },
      {
         source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
         url: "https://git.kernel.org/stable/c/0f37946c62c48a907625348cbc720a7a0c547d1e",
      },
      {
         source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
         url: "https://git.kernel.org/stable/c/2c78c9411e685dbc9eac8c2845111b03501975b8",
      },
      {
         source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
         url: "https://git.kernel.org/stable/c/8d3f83dfb23674540c827a8d65fba20aa300b252",
      },
      {
         source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
         url: "https://git.kernel.org/stable/c/e2afb26615adf6c3ceaaa7732aa839bcd587a057",
      },
      {
         source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
         url: "https://git.kernel.org/stable/c/fb6675db04c4b79883373edc578d5df7bbc84848",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "https://git.kernel.org/stable/c/0db880fc865ffb522141ced4bfa66c12ab1fbb70",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "https://git.kernel.org/stable/c/0f37946c62c48a907625348cbc720a7a0c547d1e",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "https://git.kernel.org/stable/c/2c78c9411e685dbc9eac8c2845111b03501975b8",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "https://git.kernel.org/stable/c/8d3f83dfb23674540c827a8d65fba20aa300b252",
      },
   ],
   sourceIdentifier: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
   vulnStatus: "Awaiting Analysis",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.