CVE-2024-40917 Vulnerability Analysis & Exploit Details

CVE-2024-40917
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2024-40917 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2024-40917 Details

Status: Analyzed

Last updated: 🕑 03 Oct 2025, 14:24 UTC
Originally published on: 🕐 12 Jul 2024, 13:15 UTC

Time between publication and last update: 448 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVE-2024-40917 Vulnerability Summary

CVE-2024-40917: 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.

Assessing the Risk of CVE-2024-40917

Access Complexity Graph

The exploitability of CVE-2024-40917 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2024-40917

CVE-2024-40917 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2024-40917, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2024-40917, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2024-40917 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2024-40917 poses no threat to data integrity.
  • Availability: High
    CVE-2024-40917 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.045% (probability of exploit)

EPSS Percentile: 18.4% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 81.6% of others.

CVE-2024-40917 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:6.6.70:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.70:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.71:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.71:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.9.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.9.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10:rc1:*:*:*:*:*:*
    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:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.10:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.10:rc3:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-40917: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-62672 – rplay through 3.3.2 allows attackers to cause a denial of service (SIGSEGV and daemon crash) or possibly have unspecified other impact. This occurs...
  • CVE-2025-47410 – Apache Geode is vulnerable to CSRF attacks through GET requests to the Management and Monitoring REST API that could allow an attacker who has tric...
  • CVE-2025-11926 – The Related Posts Lite plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1...
  • CVE-2025-9890 – The Theme Editor plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.0. This is due to missing...
  • CVE-2025-5555 – A vulnerability has been found in Nixdorf Wincor PORT IO Driver up to 1.0.0.1. This affects the function sub_11100 in the library wnport.sys of the...