drm/i915: clear CRTC color blob pointers after dropping refs
Summary
| CVE | CVE-2026-72452 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-15 06:22:19 UTC |
| Updated | 2026-08-17 06:19:12 UTC |
| 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) |
Risk And Classification
Primary CVSS: v3.1 7.8 HIGH from 416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS: 0.001750000 probability, percentile 0.073140000 (date 2026-08-17)
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 7.8 | HIGH | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| 3.1 | CNA | DECLARED | 7.8 | HIGH | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 9a6cbb4a5c168e94a69a0cbec572b3738205232b 164afa1a3af8e8c91b4a6d5fd7b79a44ec70abf0 git | Not specified |
| CNA | Linux | Linux | affected 8581466b827fdf0300a3e2e93900ddefd8240053 2024940522ef451098c940ab0b82d647de5e5d9b git | Not specified |
| CNA | Linux | Linux | affected 77fcf58df15edcf3f5b5421f24814fb72796def9 ac554ad943610031a25795d6ef71316f6164c136 git | Not specified |
| CNA | Linux | Linux | affected 77fcf58df15edcf3f5b5421f24814fb72796def9 31f077088e0faae6be8377741f356dea1b94ba46 git | Not specified |
| CNA | Linux | Linux | affected 674fc4a50b667be65c947d81af63a9367deafb5c git | Not specified |
| CNA | Linux | Linux | affected 6.12.80 6.12.97 semver | Not specified |
| CNA | Linux | Linux | affected 6.18.21 6.18.40 semver | Not specified |
| CNA | Linux | Linux | affected 6.19.11 6.20 semver | Not specified |
| CNA | Linux | Linux | affected 7.0 | Not specified |
| CNA | Linux | Linux | unaffected 7.0 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.97 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.40 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.5 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/164afa1a3af8e8c91b4a6d5fd7b79a44ec70abf0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ac554ad943610031a25795d6ef71316f6164c136 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/2024940522ef451098c940ab0b82d647de5e5d9b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/31f077088e0faae6be8377741f356dea1b94ba46 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.