CVE-2023-53571

drm/i915: Make intel_get_crtc_new_encoder() less oopsy

MEDIUM

5.5

CVSS Score

Published: October 4, 2025 at 03:17 PM UTC

Updated: June 17, 2026 at 06:45 AM 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

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.1%

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)

Affected

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

Linux Kernel · Linux

95%

5.11 ≤ v < 5.15.1115.16 ≤ v < 6.1.285.7 ≤ v < 5.10.1805.7 ≤ v < 5.15.1115.7 ≤ v < 6.1.285.7 ≤ v < 6.2.155.7 ≤ v < 6.3.25.7 ≤ v < 6.46.2 ≤ v < 6.2.156.3 ≤ v < 6.3.23a47ae201e074945bbde0b088e4c1215c07f4d755.7

Vendor states this is fixed in 0fe6ef82e4f4764e8f556632e4cd93d78d448e99 (fixed)

Vendor states this is fixed in 54202488c835dab8c648acd107f0bb8eaa699894 (fixed)

Vendor states this is fixed in 631420b06597a33c72b6dcef78d1c2dea17f452d (fixed)

Vendor states this is fixed in 780f303233c35eeb5132e3ee1cbc8f4cebe86dd2 (fixed)

Vendor states this is fixed in 8cd725315c559a8a4d18ac1d7fce1d6b9a667529 (fixed)

Vendor states this is fixed in fd8b0abecdf66379e9d25d7448b942b5be379cb2 (fixed)

Vendor states this is fixed in 5.10.180 (unaffected)

Vendor states this is fixed in 5.15.111 (unaffected)

Vendor states this is fixed in 5.7 (unaffected)

Vendor states this is fixed in 6.1.28 (unaffected)

Vendor states this is fixed in 6.2.15 (unaffected)

Vendor states this is fixed in 6.3.2 (unaffected)