CVE-2024-26912 Vulnerability Analysis & Exploit Details

CVE-2024-26912
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2024-26912 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-26912 Details

Status: Modified

Last updated: 🕘 21 Nov 2024, 09:03 UTC
Originally published on: 🕓 17 Apr 2024, 16:15 UTC

Time between publication and last update: 217 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-26912 Vulnerability Summary

CVE-2024-26912: In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: fix several DMA buffer leaks Nouveau manages GSP-RM DMA buffers with nvkm_gsp_mem objects. Several of these buffers are never dealloced. Some of them can be deallocated right after GSP-RM is initialized, but the rest need to stay until the driver unloads. Also futher bullet-proof these objects by poisoning the buffer and clearing the nvkm_gsp_mem object when it is deallocated. Poisoning the buffer should trigger an error (or crash) from GSP-RM if it tries to access the buffer after we've deallocated it, because we were wrong about when it is safe to deallocate. Finally, change the mem->size field to a size_t because that's the same type that dma_alloc_coherent expects.

Assessing the Risk of CVE-2024-26912

Access Complexity Graph

The exploitability of CVE-2024-26912 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-26912

CVE-2024-26912 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-26912, 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-26912, 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-26912 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2024-26912 poses no threat to data integrity.
  • Availability: High
    CVE-2024-26912 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.043% (probability of exploit)

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

CVE-2024-26912 References

External References

CWE Common Weakness Enumeration

CWE-401

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:6.7.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.5:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-26912: 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-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...
  • CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
  • CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...