LiveActive security incident?Get immediate response
CVE Record

CVE-2024-40917: memblock: make memblock_set_node() also warn about use of MAX_NUMNODES

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause a crash during early memory and NUMA setup on specific systems. The described case is an older x86 machine whose firmware reports NUMA memory only above 4GB. Business impact is mainly availability risk during boot or initialization, not a demonstrated remote compromise.

Executive priority

Handle through normal kernel patch governance unless affected hardware is business-critical or reboot reliability is already a concern. Escalate for fleets with older x86 hardware, custom kernels, or NUMA-heavy infrastructure where a boot-time crash could affect recovery windows.

Technical view

The bug involves memblock_set_node() accepting MAX_NUMNODES where NUMA_NO_NODE checks were expected. On CONFIG_NUMA=y systems with limited SRAT coverage, this can lead to memblock_alloc_range_nid() warnings and a NULL dereference in memmap_init() while accessing invalid node data.

Likely exposure

Exposure appears narrow: affected Linux kernel versions on NUMA-enabled systems with problematic ACPI SRAT memory coverage. The source bundle names Linux 6.8, 6.6.72, 6.9.6, and 6.10 as affected, but product packaging and downstream backports require vendor confirmation.

Exploitation context

The source bundle does not report active exploitation, public exploit code, or KEV listing. The described failure path is hardware or firmware configuration dependent and occurs in kernel memory initialization. Treat exploitation evidence as incomplete rather than assuming internet-facing exploitability.

Researcher notes

The core evidence is a kernel stable fix and CVE description. There is no CVSS, CWE, exploit report, or complete downstream version matrix in the bundle. Validate exposure by kernel config, ACPI SRAT behavior, and fixed commit presence, not by CVE metadata alone.

Mitigation direction

  • Apply kernel updates containing the referenced stable fixes.
  • Check your Linux vendor advisory for downstream fixed package versions.
  • Prioritize NUMA-enabled systems matching the SRAT coverage pattern described.
  • Avoid direct wrangler or deployment assumptions; this is kernel patch management.

Validation and detection

  • Identify systems running affected Linux kernel versions from the source bundle.
  • Check whether kernels are built with CONFIG_NUMA=y.
  • Review boot logs for SRAT coverage and MAX_NUMNODES-related warnings.
  • Confirm installed kernels include one of the referenced stable commits.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-40917 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6fdc770506eb8379bf68a49d4e193c8364ac64e0, ff6c3d81f2e86b63a3a530683f89ef393882782a, ff6c3d81f2e86b63a3a530683f89ef393882782a, 6.6.70unaffected
LinuxLinux6.8, 0, 6.6.72, 6.9.6, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.