CVE-2025-68193: drm/xe/guc: Add devm release action to safely tear down CT
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 XEBOFLAGGGTTINVALIDATE 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:h2gwrite+0x2f3/0x7c0 [xe] Call Trace: gucctsendlocked+0x8b/0x670 [xe] xegucctsendlocked+0x19/0x60 [xe] sendtlbinvalidation+0xb4/0x460 [xe] xegttlbinvalidationggtt+0x15e/0x2e0 [xe] ggttinvalidategttlb.part.0+0x16/0x90 [xe] ggttnoderemove+0x110/0x140 [xe] xeggttnoderemove+0x40/0xa0 [xe] xeggttremovebo+0x87/0x250 [xe]
Introduce a devm-managed release action during xegucctinit() and xegucctinitposthwconfig() to ensure proper CTB disablement before resource deallocation, preventing the use-after-free scenario.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-68193?
CVE-2025-68193 has been classified with a severity rating indicating a potential impact on system stability and security.
How do I fix CVE-2025-68193?
To fix CVE-2025-68193, you should update the Linux kernel to the latest version where this vulnerability has been resolved.
What systems are affected by CVE-2025-68193?
CVE-2025-68193 affects the Linux kernel, specifically impacting systems utilizing the affected graphics driver functionalities.
What are the potential impacts of CVE-2025-68193?
The potential impacts of CVE-2025-68193 include system crashes, instability, or compromised data integrity in systems using the vulnerable kernel version.
What types of exploitation are possible with CVE-2025-68193?
Exploitation of CVE-2025-68193 could allow an attacker to trigger TLB invalidation requests leading to denial of service conditions.