Vulnerability · Published Jun 25, 2026 · Assigned by Linux

CVE-2026-53142drm/xe/display: fix oops in suspend/shutdown without display

Medium 5.5

In plain English

A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 2% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS NVD)5.5Medium
Exploit odds (30 days)0.1%top 98.0% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official 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)

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.12.95-1DEBIAN-CVE-2026-53142
Debian:14linux7.0.13-1DEBIAN-CVE-2026-53142
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-53142
Ubuntu:25.10linuxno fix listedUBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux7.0.0-31.31UBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux7.0.0-31.31USN-8726-1
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-53142
Ubuntu:25.10linux-awsno fix listedUBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-aws7.0.0-1012.12USN-8726-1
Ubuntu:26.04:LTSlinux-aws7.0.0-1012.12UBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-aws-7.07.0.0-1012.12~24.04.1UBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-aws-7.07.0.0-1012.12~24.04.1USN-8726-1
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-53142
Ubuntu:25.10linux-azureno fix listedUBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-azure7.0.0-1014.14UBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-azure7.0.0-1014.14USN-8726-4
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-azure-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-53142
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-azure-fde7.0.0-1013.13UBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-azure-fde-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-53142
Ubuntu:25.10linux-gcpno fix listedUBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-gcp7.0.0-1011.11UBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-gcp7.0.0-1011.11USN-8726-1
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-gcp-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-gke7.0.0-1006.7UBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-gke7.0.0-1006.7USN-8726-1
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-31.31~24.04.1USN-8726-1
Ubuntu:24.04:LTSlinux-hwe-7.07.0.0-31.31~24.04.1UBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-ibm7.0.0-1013.13USN-8726-3
Ubuntu:26.04:LTSlinux-ibm7.0.0-1013.13UBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-nvidia7.0.0-1018.18USN-8760-2
Ubuntu:26.04:LTSlinux-nvidia7.0.0-1018.18UBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1018.18~24.04.1UBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-nvidia-7.07.0.0-1018.18~24.04.1USN-8760-1
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2018.18USN-8800-1
Ubuntu:26.04:LTSlinux-nvidia-bos7.0.0-2018.18UBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1013.13USN-8727-1
Ubuntu:26.04:LTSlinux-oem-7.07.0.0-1013.13UBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-53142
Ubuntu:25.10linux-oracleno fix listedUBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-oracle7.0.0-1011.11UBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-oracle7.0.0-1011.11USN-8726-4
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-oracle-7.07.0.0-1011.11~24.04.1UBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-53142
Ubuntu:25.10linux-raspino fix listedUBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-raspi7.0.0-1019.19USN-8726-2
Ubuntu:26.04:LTSlinux-raspi7.0.0-1019.19UBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-53142
Ubuntu:25.10linux-realtimeno fix listedUBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-realtime7.0.0-31.31.1UBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-realtime7.0.0-31.31.1USN-8726-1
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-53142
Ubuntu:25.10linux-riscvno fix listedUBUNTU-CVE-2026-53142
Ubuntu:26.04:LTSlinux-riscv7.0.0-31.31.1UBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-riscv-7.07.0.0-31.31.1~24.04.1UBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-53142
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-53142
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-53142

Affected products (as reported)

VendorProductVersions
Linux Linux 44e694958b95395bd1c41508c88c8ca141bf9bd7 – before ddf1fe4c043aa42e46aef87b815d5deeed2fcd7b44e694958b95395bd1c41508c88c8ca141bf9bd7 – before 0f68ddfaaebfbb5581ee931779757d31f4dc9e2444e694958b95395bd1c41508c88c8ca141bf9bd7 – before 238bcdaae8f2abc65e182de7d1f69cf8f611a61044e694958b95395bd1c41508c88c8ca141bf9bd7 – before 68938cc08e23a94fd881e845837ff918de005ce7
Linux Linux 6.8

References