5.5

CVE-2026-53142: linux Use of Uninitialized Resource

CVSS: 5.5v3.1MediumAnalyzed
AliasesUBUNTU-CVE-2026-53142DEBIAN-CVE-2026-53142CGA-26pw-fcgp-7529
Published 25-06-2026Last modified 04-07-2026

Vulnerability summary

CVE-2026-53142 is a medium (CVSS 5.5) Use of Uninitialized Resource vulnerability in linux. EPSS estimates a 0.12% chance of exploitation in the next 30 days, higher than 1.8% of scored vulnerabilities.

Overall risk
22/100
0100
Low · default modelHow is this calculated?
CVSS score
5.5/10
010
Medium · v3.1 (NVD)
EPSS score
0.12%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 19 · Related 19

Timeline

  1. 25-06-2026
    PublishedVulnerability first disclosed.
  2. 04-07-2026
    Last modifiedVulnerability information updated.

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)

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.12%

Chance of exploitation in the next 30 days

Percentile

2%

Versus all other CVEs

30-day change

0.00 pp

From 0.12% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.12%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Ubuntu142 products
  • linuxAll versions (No fix recorded) | < 7.0.0-31.31
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-awsAll versions (No fix recorded) | < 7.0.0-1012.12
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Chainguard12 products
  • linux-aws-6.12< 6.12.96-r0
  • linux-azure-6.12< 6.12.96-r0
  • linux-azure-6.18< 6.18.38-r0
  • linux-gcp-6.12< 6.12.96-r0
  • linux-gcp-6.18< 6.18.38-r0
Linux2 products
  • linux≥ 44e694958b95395bd1c41508c88c8ca141bf9bd7, < ddf1fe4c043aa42e46aef87b815d5deeed2fcd7b | ≥ 44e694958b95395bd1c41508c88c8ca141bf9bd7, < 0f68ddfaaebfbb5581ee931779757d31f4dc9e24 | ≥ 44e694958b95395bd1c41508c88c8ca141bf9bd7, < 238bcdaae8f2abc65e182de7d1f69cf8f611a610 | ≥ 44e694958b95395bd1c41508c88c8ca141bf9bd7, < 68938cc08e23a94fd881e845837ff918de005ce7 | 6.8
  • linux_kernel≥ 6.8, < 6.12.95 | ≥ 6.13, < 6.18.36 | ≥ 6.19, < 7.0.13 | 7.1:rc1 | 7.1:rc2 | 7.1:rc3 | 7.1:rc4 | 7.1:rc5 | 7.1:rc6 | 7.1:rc7
Debian1 product
  • linux< 6.12.95-1 | < 7.0.13-1

4 vendors · 157 products

References

19 links
Show all 19 references