CVE-2026-72452

drm/i915: clear CRTC color blob pointers after dropping refs

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 05:57 AM UTC
Updated: October 16, 2026 at 07:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: drm/i915: clear CRTC color blob pointers after dropping refs intel_crtc_put_color_blobs() drops the CRTC color blob references, but leaves the corresponding pointers unchanged. This can matter in intel_crtc_prepare_cleared_state(), which frees the old CRTC hw state before calling intel_dp_tunnel_atomic_clear_stream_bw(). The latter can fail while looking up the DP tunnel group state, for example with -EDEADLK. If that happens, the function returns without completing the cleared state preparation. The failed atomic state will then be cleared by the atomic core and intel_crtc_free_hw_state() can be called again for the same state, dropping the same blob references again. Clear the blob pointers after dropping the references so repeated cleanup of the same CRTC hw state is safe. (cherry picked from commit d5005addb5f68e8a0edce249506757bdc9e3d8c8)

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.12.806.18.216.19.11674fc4a50b667be65c947d81af63a9367deafb5c7.077fcf58df15edcf3f5b5421f24814fb72796def98581466b827fdf0300a3e2e93900ddefd82400539a6cbb4a5c168e94a69a0cbec572b3738205232b
Vendor states this is fixed in 164afa1a3af8e8c91b4a6d5fd7b79a44ec70abf0 (fixed)
Vendor states this is fixed in 2024940522ef451098c940ab0b82d647de5e5d9b (fixed)
Vendor states this is fixed in 31f077088e0faae6be8377741f356dea1b94ba46 (fixed)
Vendor states this is fixed in ac554ad943610031a25795d6ef71316f6164c136 (fixed)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Affected range stops below 6.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 7.0 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card