CVE-2024-40917memblock: make memblock_set_node() also warn about use of MAX_NUMNODES
- 5.5MediumCVSS base score
- 0.26%Exploitation in 30 daysEPSS · top 81% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In 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.
Timeline
ID reserved
By Linux
Published
- 23 months later
· 23 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.26% · top 81% of all CVEs (14 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 6fdc770506eb8379bf68a49d4e193c8364ac64e0 – < 4ddb7f966f3d06fcf1ba5ee298af6714b593584b
- affected ff6c3d81f2e86b63a3a530683f89ef393882782a – < 22f742b8f738918f683198a18ec3c691acda14c4
- affected ff6c3d81f2e86b63a3a530683f89ef393882782a – < e0eec24e2e199873f43df99ec39773ad3af2bff7
- affected 6.6.70 – < 6.6.72
- affected 6.8
- unaffected < 6.8
- unaffected 6.6.72 – ≤ 6.6.*
- unaffected 6.9.6 – ≤ 6.9.*
- unaffected 6.10 – ≤ *
References
References3
- https://git.kernel.org/stable/c/4ddb7f966f3d06fcf1ba5ee298af6714b593584b (opens in a new tab)
- https://git.kernel.org/stable/c/22f742b8f738918f683198a18ec3c691acda14c4 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/e0eec24e2e199873f43df99ec39773ad3af2bff7 (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-38728 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-40917)Record last updated .