Back
CVE-2023-53571
drm/i915: Make intel_get_crtc_new_encoder() less oopsy
Medium5.5EPSS 0.15%
- Published
- Updated
- Reserved
- Assigned by
- Linux
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)
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.15% · top 96% of all CVEs (6 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 3a47ae201e074945bbde0b088e4c1215c07f4d75 – < 780f303233c35eeb5132e3ee1cbc8f4cebe86dd2
- affected 3a47ae201e074945bbde0b088e4c1215c07f4d75 – < 54202488c835dab8c648acd107f0bb8eaa699894
- affected 3a47ae201e074945bbde0b088e4c1215c07f4d75 – < 0fe6ef82e4f4764e8f556632e4cd93d78d448e99
- affected 3a47ae201e074945bbde0b088e4c1215c07f4d75 – < 8cd725315c559a8a4d18ac1d7fce1d6b9a667529
- affected 3a47ae201e074945bbde0b088e4c1215c07f4d75 – < fd8b0abecdf66379e9d25d7448b942b5be379cb2
- affected 3a47ae201e074945bbde0b088e4c1215c07f4d75 – < 631420b06597a33c72b6dcef78d1c2dea17f452d
- affected 5.7
- unaffected < 5.7
- unaffected 5.10.180 – ≤ 5.10.*
- unaffected 5.15.111 – ≤ 5.15.*
- unaffected 6.1.28 – ≤ 6.1.*
- unaffected 6.2.15 – ≤ 6.2.*
- unaffected 6.3.2 – ≤ 6.3.*
- unaffected 6.4 – ≤ *
References (6)
- https://git.kernel.org/stable/c/780f303233c35eeb5132e3ee1cbc8f4cebe86dd2 (opens in a new tab)
- https://git.kernel.org/stable/c/54202488c835dab8c648acd107f0bb8eaa699894 (opens in a new tab)
- https://git.kernel.org/stable/c/0fe6ef82e4f4764e8f556632e4cd93d78d448e99 (opens in a new tab)
- https://git.kernel.org/stable/c/8cd725315c559a8a4d18ac1d7fce1d6b9a667529 (opens in a new tab)
- https://git.kernel.org/stable/c/fd8b0abecdf66379e9d25d7448b942b5be379cb2 (opens in a new tab)
- https://git.kernel.org/stable/c/631420b06597a33c72b6dcef78d1c2dea17f452d (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2023-53571)Record last updated .