CVE-2026-53142
Last modified
CVE-2026-53142 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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(). EPSS estimates a 0.17% chance of exploitation in the next 30 days.
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)
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.8, < 6.12.95 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.36 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.13 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53142?
How severe is CVE-2026-53142?
How do I fix CVE-2026-53142?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53137In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53138In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-53139In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-5314A vulnerability was found in Nothings stb up to 1.26. Impact…8.8
- CVE-2026-53140In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53141In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53143In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53144In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53145In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53146In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-53147In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-53148In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-53142?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
