# CVE-2026-97519: drm/xe: Fix null pointer dereference in devcoredump cleanup

> A null pointer dereference in the Linux kernel's Xe GPU driver devcoredump cleanup can cause a system crash, requiring local access to trigger.

- **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:** 24 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** AZL-103961, BELL-CVE-2026-97519, DEBIAN-CVE-2026-97519, GHSA-847m-qmx9-284v, UBUNTU-CVE-2026-97519

## What is CVE-2026-97519?

CVE-2026-97519 is a vulnerability in Linux, published on 24 Sep 2026. 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: Fix null pointer dereference in devcoredump cleanup

In xe_devcoredump_snapshot_free(), ss->gt may be NULL when the snapshot
was never fully populated (e.g., when cleanup is triggered without a
prior capture). Guard the xe_guc_capture_put_matched_nodes() call with
IS_ERR_OR_NULL() to prevent a null dereference.

In xe_devcoredump_free(), the deferred work is only queued when a
coredump is captured, so guard cancel_work_sync() with a check on
coredump->captured.

## Which versions are affected by CVE-2026-97519?


## How do I fix CVE-2026-97519?

Apply the vendor's patch.

## Is CVE-2026-97519 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97519 and fix it if it is affected.

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

## Sources

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

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