# CVE-2026-80915: drm/xe: Fix DPT allocation paths.

> A flaw in the Linux kernel's Xe GPU driver causes system hangs or black screens due to improper memory allocation, requiring a kernel patch.

- **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:** 9 Sep 2026
- **Updated:** 9 Sep 2026
- **Also known as:** BELL-CVE-2026-80915, DEBIAN-CVE-2026-80915, GHSA-whqc-hpw3-72pp, UBUNTU-CVE-2026-80915

## What is CVE-2026-80915?

CVE-2026-80915 is a denial of service vulnerability in Linux, published on 9 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 DPT allocation paths.

Remove the fallback for VRAM to system memory, I tested it and that
doesn't work at all, only a black screen with pipe fault errors were
observed.

On systems with media GT, extra latency is added when accessing stolen
memory when the GT is in MC6. Since we additionally aren't counting how
much memory is used for stolen and we could in theory fill up the
entire stolen area with DPT's, avoid using stolen and only use the
default memory region.

Using stolen may also result in random system hangs under load.

(cherry picked from commit a196406a3831291598fe8e73245914f7acffdfe0)

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


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

Apply the vendor's patch.

## Is CVE-2026-80915 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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