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

> A use-after-free in the Linux kernel's Xe GPU driver allows local attackers to cause a system crash via premature buffer release.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Dec 2025
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2025-68193, DEBIAN-CVE-2025-68193, GHSA-rcqc-4q5v-hpcm, ROOT-OS-DEBIAN-13-CVE-2025-68193, ROOT-OS-UBUNTU-2204-CVE-2025-68193, ROOT-OS-UBUNTU-2404-CVE-2025-68193, UBUNTU-CVE-2025-68193

## What is CVE-2025-68193?

CVE-2025-68193 is an use after free vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2025-68193?


## How do I fix CVE-2025-68193?

Apply the vendor's patch.

## Is CVE-2025-68193 being exploited?

There is no known exploitation of CVE-2025-68193 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68193 and fix it if it is affected.

What it is: CVE-2025-68193 is an use after free vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68193 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68193/ (Markdown: https://insights.sbomify.com/CVE-2025-68193/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68193
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68193
- OSV: https://osv.dev/vulnerability/CVE-2025-68193

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68193/
Summaries are generated and may contain mistakes; the official description above is the record.