CVE-2026-80705

What it actually does

Missing success check after dml21_add_phantom_plane() allocation allows a null pointer to be dereferenced later, resulting in a segmentation fault in the AMD display driver.

Why it matters to the business

Unexpected kernel crashes or display instability on AMD-based Linux systems can interrupt workloads, require reboots, and reduce system availability.

How an attack unfolds

An attacker with local access crafts display or graphics operations that cause phantom-plane allocation to fail; the unchecked null return value is later used, triggering a segfault.

How to fix it

Update to a Linux kernel containing the fix that verifies the return value of dml21_add_phantom_plane() before use.

How to confirm the fix worked

Confirm the kernel source or binary contains the added success check around dml21_add_phantom_plane(); inspect dmesg or kernel logs for absence of related null-dereference panics after graphics operations.

Typical attack path

1. Obtain local user access on a Linux system with AMD display hardware
2. Trigger display code paths that invoke dml21_add_phantom_plane()
3. Force allocation failure conditions
4. Reach the subsequent dereference of the unchecked pointer

How to detect it

Review kernel panic and oops logs for drm/amd/display entries mentioning phantom plane or null dereference; correlate with graphics initialization events.

What your security team should do

• Apply the upstream AMD display driver fix at the next kernel update window
• Monitor EPSS and exploit maturity indicators for any change
• Test graphics-intensive workloads on patched kernels before broad deployment