CVE-2024-26721 Vulnerability Analysis & Exploit Details

CVE-2024-26721
Vulnerability Scoring

5.5
/10
Significant Risk

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

Status: Analyzed

Last updated: 🕓 17 Mar 2025, 16:01 UTC
Originally published on: 🕒 03 Apr 2024, 15:15 UTC

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

CVE-2024-26721: In the Linux kernel, the following vulnerability has been resolved: drm/i915/dsc: Fix the macro that calculates DSCC_/DSCA_ PPS reg address Commit bd077259d0a9 ("drm/i915/vdsc: Add function to read any PPS register") defines a new macro to calculate the DSC PPS register addresses with PPS number as an input. This macro correctly calculates the addresses till PPS 11 since the addresses increment by 4. So in that case the following macro works correctly to give correct register address: _MMIO(_DSCA_PPS_0 + (pps) * 4) However after PPS 11, the register address for PPS 12 increments by 12 because of RC Buffer memory allocation in between. Because of this discontinuity in the address space, the macro calculates wrong addresses for PPS 12 - 16 resulting into incorrect DSC PPS parameter value read/writes causing DSC corruption. This fixes it by correcting this macro to add the offset of 12 for PPS >=12. v3: Add correct paranthesis for pps argument (Jani Nikula) (cherry picked from commit 6074be620c31dc2ae11af96a1a5ea95580976fb5)

Assessing the Risk of CVE-2024-26721

Access Complexity Graph

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

CVE-2024-26721 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-26721, 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-26721, 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-26721 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2024-26721 poses no threat to data integrity.
  • Availability: High
    CVE-2024-26721 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: 12.0% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 88.0% of others.

CVE-2024-26721 References

External References

CWE Common Weakness Enumeration

CWE-131

CAPEC Common Attack Pattern Enumeration and Classification

  • Overflow Buffers CAPEC-100 Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an adversary. As a consequence, an adversary is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the adversaries' choice.
  • Buffer Overflow via Parameter Expansion CAPEC-47 In this attack, the target software is given input that the adversary knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:6.7:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:-:*:*:*:*:*:*
  • 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:*:*:*:*:*:*:*
  • 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:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-26721: 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-4250 – A vulnerability was found in code-projects Nero Social Networking Site 1.0. It has been classified as critical. This affects an unknown part of the...
  • CVE-2025-4249 – A vulnerability was found in PHPGurukul e-Diary Management System 1.0 and classified as critical. Affected by this issue is some unknown functional...
  • CVE-2025-4248 – A vulnerability has been found in SourceCodester Simple To-Do List System 1.0 and classified as critical. Affected by this vulnerability is an unkn...
  • CVE-2025-4247 – A vulnerability, which was classified as critical, was found in SourceCodester Simple To-Do List System 1.0. Affected is an unknown function of the...
  • CVE-2025-47245 – In BlueWave Checkmate through 2.0.2 before d4a6072, an invite request can be modified to specify a privileged role.