CVE-2026-53142: Linux kernel · drm/xe/display: fix oops in suspend/shutdown without display
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ddf1fe4c043aa42e46aef87b815d5deeed2fcd7b : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:49 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in ddf1fe4c043aa42e46aef87b815d5deeed2fcd7b, 68938cc08e23a94fd881e845837ff918de005ce7, 238bcdaae8f2abc65e182de7d1f69cf8f611a610 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade Linux kernel to ddf1fe4c043aa42e46aef87b815d5deeed2fcd7b, 68938cc08e23a94fd881e845837ff918de005ce7, 238bcdaae8f2abc65e182de7d1f69cf8f611a610 or 0f68ddfaaebfbb5581ee931779757d31f4dc9e24.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: drm/xe/display: fix oops in suspend/shutdown without display The xe driver keeps track of whether to probe display, and whether display hardware is there, using xe->info.probe_display. It gets set to false if there's no display after intel_display_device_probe(). However, the display may also be disabled via fuses, detected at a later time in intel_display_device_info_runtime_init(). In this case, the xe driver does for_each_intel_crtc() on uninitialized mode config in xe_display_flush_cleanup_work(), leading to a NULL pointer dereference, and generally calls display code with display info cleared. Check for intel_display_device_present() after intel_display_device_info_runtime_init(), and reset xe->info.probe_display as necessary. Also do unset_display_features() for completeness, although display runtime init has already done that. This will need to be unified across all cases later. Move intel_display_device_info_runtime_init() call slightly earlier, similar to i915, to avoid a bunch of unnecessary setup for no display cases. Note #1: The xe driver has no business doing low level display plumbing like for_each_intel_crtc() to begin with. It all needs to happen in display code. Note #2: The actual bug is present already in commit 44e694958b95 ("drm/xe/display: Implement display support"), but the oops was likely introduced later at commit ddf6492e0e50 ("drm/xe/display: Make display suspend/resume work on discrete"). (cherry picked from commit 7c3eb9f47533220888a67266448185fd0775d4da)
References
- git.kernel.org/stable/c/ddf1fe4c043aa42e46aef87b815d5deeed2fcd7b (opens in a new tab)
- git.kernel.org/stable/c/0f68ddfaaebfbb5581ee931779757d31f4dc9e24 (opens in a new tab)
- git.kernel.org/stable/c/238bcdaae8f2abc65e182de7d1f69cf8f611a610 (opens in a new tab)
- git.kernel.org/stable/c/68938cc08e23a94fd881e845837ff918de005ce7 (opens in a new tab)