---
id: CVE-2023-53571
title: 'drm/i915: Make intel_get_crtc_new_encoder() less oopsy'
summary: |-
  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 …
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 3a47ae201e074945bbde0b088e4c1215c07f4d75 <
    780f303233c35eeb5132e3ee1cbc8f4cebe86dd2
  - >-
    Linux >= 3a47ae201e074945bbde0b088e4c1215c07f4d75 <
    54202488c835dab8c648acd107f0bb8eaa699894
  - >-
    Linux >= 3a47ae201e074945bbde0b088e4c1215c07f4d75 <
    0fe6ef82e4f4764e8f556632e4cd93d78d448e99
  - >-
    Linux >= 3a47ae201e074945bbde0b088e4c1215c07f4d75 <
    8cd725315c559a8a4d18ac1d7fce1d6b9a667529
  - >-
    Linux >= 3a47ae201e074945bbde0b088e4c1215c07f4d75 <
    fd8b0abecdf66379e9d25d7448b942b5be379cb2
  - >-
    Linux >= 3a47ae201e074945bbde0b088e4c1215c07f4d75 <
    631420b06597a33c72b6dcef78d1c2dea17f452d
  - Linux 5.7
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-11-05T20:23:55.527114Z'
published: '2025-10-04'
updated: '2026-11-05'
sourceUpdated: '2026-11-05T20:31:15.021Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2023-53571'
references:
  - url: 'https://git.kernel.org/stable/c/780f303233c35eeb5132e3ee1cbc8f4cebe86dd2'
  - url: 'https://git.kernel.org/stable/c/54202488c835dab8c648acd107f0bb8eaa699894'
  - url: 'https://git.kernel.org/stable/c/0fe6ef82e4f4764e8f556632e4cd93d78d448e99'
  - url: 'https://git.kernel.org/stable/c/8cd725315c559a8a4d18ac1d7fce1d6b9a667529'
  - url: 'https://git.kernel.org/stable/c/fd8b0abecdf66379e9d25d7448b942b5be379cb2'
  - url: 'https://git.kernel.org/stable/c/631420b06597a33c72b6dcef78d1c2dea17f452d'
tags:
  - cve.org
epss: 0.00149
epssPercentile: 0.04068
ingestedAt: '2026-11-05T22:38:31.812Z'
---

## Overview

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

- `Linux >= 3a47ae201e074945bbde0b088e4c1215c07f4d75 < 780f303233c35eeb5132e3ee1cbc8f4cebe86dd2`
- `Linux >= 3a47ae201e074945bbde0b088e4c1215c07f4d75 < 54202488c835dab8c648acd107f0bb8eaa699894`
- `Linux >= 3a47ae201e074945bbde0b088e4c1215c07f4d75 < 0fe6ef82e4f4764e8f556632e4cd93d78d448e99`
- `Linux >= 3a47ae201e074945bbde0b088e4c1215c07f4d75 < 8cd725315c559a8a4d18ac1d7fce1d6b9a667529`
- `Linux >= 3a47ae201e074945bbde0b088e4c1215c07f4d75 < fd8b0abecdf66379e9d25d7448b942b5be379cb2`
- `Linux >= 3a47ae201e074945bbde0b088e4c1215c07f4d75 < 631420b06597a33c72b6dcef78d1c2dea17f452d`
- `Linux 5.7`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.