CVE-2024-26913

What it actually does

Missing ODM calculation in pipe split policy determination for DCN35 hardware leads to display underflow and memory corruption during high-resolution modes such as 8K30.

Why it matters to the business

Local users on affected Linux systems with AMD DCN35 graphics can trigger display corruption or kernel-level instability, potentially leading to loss of availability or escalation of privileges on graphics workloads.

How an attack unfolds

An attacker with local access configures a display mode that exercises the incomplete pipe-split logic, causing the kernel display driver to miscalculate ODM parameters and corrupt display buffers or trigger underflow conditions.

How to fix it

Update the Linux kernel to the commit cdbe0be8874c63bca85b8c38e5b1eecbdd18df31 or later stable releases that include the ODM calculation fix for dcn35 pipe split policy.

How to confirm the fix worked

Verify the running kernel contains commit cdbe0be8874c63bca85b8c38e5b1eecbdd18df31 and test 8K30 display configurations to confirm absence of underflow or corruption.

Typical attack path

1. Obtain local user access on a Linux system with AMD DCN35 hardware
2. Load or trigger a display configuration using 8K30 or similar high-bandwidth mode
3. Invoke the display driver path that omits ODM calculation for pipe split policy
4. Induce underflow or memory corruption to impact system stability or escalate privileges

How to detect it

Review kernel logs for display driver underflow or corruption messages on systems with AMD DCN35 hardware; no public exploit artifacts are known.

What your security team should do

• Prioritize kernel upgrades on all systems using AMD DCN35 graphics hardware
• Apply the fix within normal patch windows given low EPSS and absence from KEV
• Monitor for future backports to distribution kernels and rebuild custom kernels if necessary