From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72452: drm/i915: clear CRTC color blob pointers after dropping refs
Date: Sat, 15 Aug 2026 15:08:51 +0900 [thread overview]
Message-ID: <2026081531-CVE-2026-72452-200c@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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)
The Linux kernel CVE team has assigned CVE-2026-72452 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12.80 with commit 9a6cbb4a5c168e94a69a0cbec572b3738205232b and fixed in 6.12.97 with commit 164afa1a3af8e8c91b4a6d5fd7b79a44ec70abf0
Issue introduced in 6.18.21 with commit 8581466b827fdf0300a3e2e93900ddefd8240053 and fixed in 6.18.40 with commit 2024940522ef451098c940ab0b82d647de5e5d9b
Issue introduced in 7.0 with commit 77fcf58df15edcf3f5b5421f24814fb72796def9 and fixed in 7.1.5 with commit ac554ad943610031a25795d6ef71316f6164c136
Issue introduced in 7.0 with commit 77fcf58df15edcf3f5b5421f24814fb72796def9 and fixed in 7.2-rc1 with commit 31f077088e0faae6be8377741f356dea1b94ba46
Issue introduced in 6.19.11 with commit 674fc4a50b667be65c947d81af63a9367deafb5c
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-72452
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/gpu/drm/i915/display/intel_atomic.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/164afa1a3af8e8c91b4a6d5fd7b79a44ec70abf0
https://git.kernel.org/stable/c/2024940522ef451098c940ab0b82d647de5e5d9b
https://git.kernel.org/stable/c/ac554ad943610031a25795d6ef71316f6164c136
https://git.kernel.org/stable/c/31f077088e0faae6be8377741f356dea1b94ba46
reply other threads:[~2026-08-15 6:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026081531-CVE-2026-72452-200c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.