CVE-2024-40917

  1. Yack CVE
  2. Vulnerabilities (CVE)
  3. CVE-2024-40917

5.5 /10

CVSS v3 : MEDIUM

V3 Legend

Vector :

Exploitability : 1.8 / Impact : 3.6

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

I

n the Linux kernel, the following vulnerability has been resolved: memblock: make memblock_set_node() also warn about use of MAX_NUMNODES On an (old) x86 system with SRAT just covering space above 4Gb: ACPI: SRAT: Node 0 PXM 0 [mem 0x100000000-0xfffffffff] hotplug the commit referenced below leads to this NUMA configuration no longer being refused by a CONFIG_NUMA=y kernel (previously NUMA: nodes only cover 6144MB of your 8185MB e820 RAM. Not used. No NUMA configuration found Faking a node at [mem 0x0000000000000000-0x000000027fffffff] was seen in the log directly after the message quoted above), because of memblock_validate_numa_coverage() checking for NUMA_NO_NODE (only). This in turn led to memblock_alloc_range_nid()'s warning about MAX_NUMNODES triggering, followed by a NULL deref in memmap_init() when trying to access node 64's (NODE_SHIFT=6) node data. To compensate said change, make memblock_set_node() warn on and adjust a passed in value of MAX_NUMNODES, just like various other functions already do.

References
Link Resource
https://git.kernel.org/stable/c/22f742b8f738918f683198a18ec3c691acda14c4 Patch
https://git.kernel.org/stable/c/4ddb7f966f3d06fcf1ba5ee298af6714b593584b Patch
https://git.kernel.org/stable/c/e0eec24e2e199873f43df99ec39773ad3af2bff7 Patch
https://git.kernel.org/stable/c/22f742b8f738918f683198a18ec3c691acda14c4 Patch
https://git.kernel.org/stable/c/e0eec24e2e199873f43df99ec39773ad3af2bff7 Patch
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.10:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.10:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.10:rc3:*:*:*:*:*:*
History

03 Oct 2025, 14:24

Type Values Removed Values Added
CPE cpe:2.3:o:linux:linux_kernel:6.10:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.10:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.10:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
References () https://git.kernel.org/stable/c/22f742b8f738918f683198a18ec3c691acda14c4 - () https://git.kernel.org/stable/c/22f742b8f738918f683198a18ec3c691acda14c4 - Patch
References () https://git.kernel.org/stable/c/4ddb7f966f3d06fcf1ba5ee298af6714b593584b - () https://git.kernel.org/stable/c/4ddb7f966f3d06fcf1ba5ee298af6714b593584b - Patch
References () https://git.kernel.org/stable/c/e0eec24e2e199873f43df99ec39773ad3af2bff7 - () https://git.kernel.org/stable/c/e0eec24e2e199873f43df99ec39773ad3af2bff7 - Patch
First Time Linux linux Kernel
Linux
CWE NVD-CWE-noinfo
CVSS v2 : unknown
v3 : unknown 		v2 : unknown
v3 : 5.5

17 Jan 2025, 14:15

Type Values Removed Values Added
References
  • () https://git.kernel.org/stable/c/4ddb7f966f3d06fcf1ba5ee298af6714b593584b -

21 Nov 2024, 09:31

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/22f742b8f738918f683198a18ec3c691acda14c4 - () https://git.kernel.org/stable/c/22f742b8f738918f683198a18ec3c691acda14c4 -
References () https://git.kernel.org/stable/c/e0eec24e2e199873f43df99ec39773ad3af2bff7 - () https://git.kernel.org/stable/c/e0eec24e2e199873f43df99ec39773ad3af2bff7 -
Summary
  • (es) En el kernel de Linux, se resolvió la siguiente vulnerabilidad: memblock: make memblock_set_node() también advierte sobre el uso de MAX_NUMNODES En un sistema x86 (antiguo) con SRAT que solo cubre espacio superior a 4 Gb: ACPI: SRAT: Nodo 0 PXM 0 [mem 0x100000000 -0xfffffffff] hotplug, El commit a la que se hace referencia a continuación hace que esta configuración NUMA ya no sea rechazada por un kernel CONFIG_NUMA=y (anteriormente NUMA: los nodos solo cubren 6144 MB de su RAM e820 de 8185 MB. No se usa. No se encontró ninguna configuración NUMA Falsificar un nodo en [mem 0x0000000000000000-0x000000027fffffff] se vio en el registro directamente después del mensaje citado anteriormente), debido a que memblock_validate_numa_coverage() verifica NUMA_NO_NODE (solamente). Esto a su vez llevó a la advertencia de memblock_alloc_range_nid() sobre la activación de MAX_NUMNODES, seguida de una deref NULL en memmap_init() al intentar acceder a los datos del nodo 64 (NODE_SHIFT=6). Para compensar dicho cambio, active memblock_set_node() y ajuste un valor pasado de MAX_NUMNODES, tal como lo hacen otras funciones.

12 Jul 2024, 13:15

Type Values Removed Values Added
New CVE
Information

Published : 2024-07-12 13:15

Updated : 2025-10-03 14:24

NVD link : CVE-2024-40917

Mitre link : CVE-2024-40917

CVE.ORG link : CVE-2024-40917

JSON object : View

Products Affected

linux

CWE
NVD-CWE-noinfo