CVE-2026-72452: drm/i915: clear CRTC color blob pointers after dropping refs
In the Linux kernel, the following vulnerability has been resolved:
drm/i915: clear CRTC color blob pointers after dropping refs
intelcrtcputcolorblobs() drops the CRTC color blob references, but leaves the corresponding pointers unchanged.
This can matter in intelcrtcprepareclearedstate(), which frees the old CRTC hw state before calling inteldptunnelatomicclearstreambw(). 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 intelcrtcfreehwstate() 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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-aws-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1014.14~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-fde-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1016.16~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1014.14~24.04.1 - Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-38.38~24.04.4 - Upgrade
Upgrade
ubuntu/linux-oracle-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1013.13~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-38.38 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-azure-fdeto a version that resolves this vulnerability.Fixed in 7.0.0-1016.16 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1014.14 - Upgrade
Upgrade
ubuntu/linux-gketo a version that resolves this vulnerability.Fixed in 7.0.0-1008.9 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1015.15 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1015.15 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1013.13 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-38.38.1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.97 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.40 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.1.5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch d5005addb5f68e8a0edce249506757bdc9e3d8c8
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72452?
CVE-2026-72452 has a risk score of 26, indicating a critical vulnerability in the Linux kernel.
How do I fix CVE-2026-72452?
To fix CVE-2026-72452, it is recommended to update to the latest version of the Linux kernel where this vulnerability has been resolved.
What systems are affected by CVE-2026-72452?
CVE-2026-72452 affects systems running the Linux kernel with the Intel DRM/i915 driver.
What is the impact of CVE-2026-72452?
The impact of CVE-2026-72452 could include potential denial of service or security breaches in systems using the affected driver.
Who reported or discovered CVE-2026-72452?
Details on the individual or organization that reported CVE-2026-72452 are not specified in the vulnerability disclosure.