linux-cve-announce - CVE-2023-53571: drm/i915: Make intel_get_crtc_new

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025100453-CVE-2023-53571-3269@gregkh>
Date: Sat,  4 Oct 2025 17:17:25 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53571: drm/i915: Make intel_get_crtc_new_encoder() less oopsy

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

drm/i915: Make intel_get_crtc_new_encoder() less oopsy

The point of the WARN was to print something, not oops
straight up. Currently that is precisely what happens
if we can't find the connector for the crtc in the atomic
state. Get the dev pointer from the atomic state instead
of the potentially NULL encoder to avoid that.

(cherry picked from commit 3b6692357f70498f617ea1b31a0378070a0acf1c)

The Linux kernel CVE team has assigned CVE-2023-53571 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.7 with commit 3a47ae201e074945bbde0b088e4c1215c07f4d75 and fixed in 5.10.180 with commit 780f303233c35eeb5132e3ee1cbc8f4cebe86dd2
	Issue introduced in 5.7 with commit 3a47ae201e074945bbde0b088e4c1215c07f4d75 and fixed in 5.15.111 with commit 54202488c835dab8c648acd107f0bb8eaa699894
	Issue introduced in 5.7 with commit 3a47ae201e074945bbde0b088e4c1215c07f4d75 and fixed in 6.1.28 with commit 0fe6ef82e4f4764e8f556632e4cd93d78d448e99
	Issue introduced in 5.7 with commit 3a47ae201e074945bbde0b088e4c1215c07f4d75 and fixed in 6.2.15 with commit 8cd725315c559a8a4d18ac1d7fce1d6b9a667529
	Issue introduced in 5.7 with commit 3a47ae201e074945bbde0b088e4c1215c07f4d75 and fixed in 6.3.2 with commit fd8b0abecdf66379e9d25d7448b942b5be379cb2
	Issue introduced in 5.7 with commit 3a47ae201e074945bbde0b088e4c1215c07f4d75 and fixed in 6.4 with commit 631420b06597a33c72b6dcef78d1c2dea17f452d

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-2023-53571
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_display.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/780f303233c35eeb5132e3ee1cbc8f4cebe86dd2
	https://git.kernel.org/stable/c/54202488c835dab8c648acd107f0bb8eaa699894
	https://git.kernel.org/stable/c/0fe6ef82e4f4764e8f556632e4cd93d78d448e99
	https://git.kernel.org/stable/c/8cd725315c559a8a4d18ac1d7fce1d6b9a667529
	https://git.kernel.org/stable/c/fd8b0abecdf66379e9d25d7448b942b5be379cb2
	https://git.kernel.org/stable/c/631420b06597a33c72b6dcef78d1c2dea17f452d