# CVE-2025-68326: drm/xe/guc: Fix stack_depot usage

> A missing initialization in the Linux kernel Xe GPU driver causes a null pointer dereference and system crash when debug mode is enabled.

- **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:** 22 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-68326, DEBIAN-CVE-2025-68326, GHSA-7gr6-fx87-x7p2, UBUNTU-CVE-2025-68326

## What is CVE-2025-68326?

CVE-2025-68326 is a vulnerability in Linux, published on 22 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: Fix stack_depot usage

Add missing stack_depot_init() call when CONFIG_DRM_XE_DEBUG_GUC is
enabled to fix the following call stack:

	[] BUG: kernel NULL pointer dereference, address: 0000000000000000
	[] Workqueue:  drm_sched_run_job_work [gpu_sched]
	[] RIP: 0010:stack_depot_save_flags+0x172/0x870
	[] Call Trace:
	[]  <TASK>
	[]  fast_req_track+0x58/0xb0 [xe]

(cherry picked from commit 64fdf496a6929a0a194387d2bb5efaf5da2b542f)

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


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

Apply the vendor's patch.

## Is CVE-2025-68326 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68326 is a vulnerability in Linux, published on 22 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-68326 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-68326/ (Markdown: https://insights.sbomify.com/CVE-2025-68326/index.md)
```

## Sources

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

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