CVE-2023-53571
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-04

Last updated on: 2026-03-21

Assigner: kernel.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)
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-04
Last Modified
2026-03-21
Generated
2026-05-07
AI Q&A
2025-10-04
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel From 5.15.160 (inc) to 5.16 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is in the Linux kernel's drm/i915 component. It involves the function intel_get_crtc_new_encoder(), which currently causes a kernel oops (a serious error) when it cannot find the connector for the CRTC (display controller) in the atomic state. The intended behavior was to print a warning (WARN) message, not to cause an oops. The fix changes the code to get the device pointer from the atomic state instead of a potentially NULL encoder, preventing the oops.


How can this vulnerability impact me? :

This vulnerability can cause the Linux kernel to crash (kernel oops) when the drm/i915 driver fails to find the connector for a display controller in the atomic state. This can lead to system instability or crashes, potentially disrupting normal operation of the system using this driver.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart