Skip to main content
VulnerabilityPublished Updated

CVE-2025-68193: Linux kernel · drm/xe/guc: Add devm release action to safely tear down CT

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in fd4e41545d5955e6f7b4a0c4b56d21010ce8e812 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in fd4e41545d5955e6f7b4a0c4b56d21010ce8e812, ee4b32220a6b41e71512e8804585325e685456ba, 52faa05fcd9f78af99abebe30a4b7b444744c991

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade Linux kernel to fd4e41545d5955e6f7b4a0c4b56d21010ce8e812, ee4b32220a6b41e71512e8804585325e685456ba or 52faa05fcd9f78af99abebe30a4b7b444744c991.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 231c4110873a5db4975512c30aa10edcc5be56e2, < fd4e41545d5955e6f7b4a0c4b56d21010ce8e812
Fixed in
  • fd4e41545d5955e6f7b4a0c4b56d21010ce8e812
LinuxLinuxAffected
  • ≥ 231c4110873a5db4975512c30aa10edcc5be56e2, < ee4b32220a6b41e71512e8804585325e685456ba
Fixed in
  • ee4b32220a6b41e71512e8804585325e685456ba
LinuxLinuxAffected
  • ≥ 231c4110873a5db4975512c30aa10edcc5be56e2, < 52faa05fcd9f78af99abebe30a4b7b444744c991
Fixed in
  • 52faa05fcd9f78af99abebe30a4b7b444744c991
LinuxLinuxAffected
  • =6.10
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: drm/xe/guc: Add devm release action to safely tear down CT When a buffer object (BO) is allocated with the XE_BO_FLAG_GGTT_INVALIDATE flag, the driver initiates TLB invalidation requests via the CTB mechanism while releasing the BO. However a premature release of the CTB BO can lead to system crashes, as observed in: Oops: Oops: 0000 [#1] SMP NOPTI RIP: 0010:h2g_write+0x2f3/0x7c0 [xe] Call Trace: guc_ct_send_locked+0x8b/0x670 [xe] xe_guc_ct_send_locked+0x19/0x60 [xe] send_tlb_invalidation+0xb4/0x460 [xe] xe_gt_tlb_invalidation_ggtt+0x15e/0x2e0 [xe] ggtt_invalidate_gt_tlb.part.0+0x16/0x90 [xe] ggtt_node_remove+0x110/0x140 [xe] xe_ggtt_node_remove+0x40/0xa0 [xe] xe_ggtt_remove_bo+0x87/0x250 [xe] Introduce a devm-managed release action during xe_guc_ct_init() and xe_guc_ct_init_post_hwconfig() to ensure proper CTB disablement before resource deallocation, preventing the use-after-free scenario.

References

Community reviews

Loading reviews…