# CVE-2026-90064: drm/xe: Reject page faults from non-fault-mode scratch VMs

> A local attacker can cause an indefinite GPU retry loop and denial of service by triggering page faults on non-fault-mode scratch VMs in the Linux kernel.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-90064, GHSA-3jfv-m5vm-v4f6, UBUNTU-CVE-2026-90064

## What is CVE-2026-90064?

CVE-2026-90064 is a denial of service vulnerability in Linux, published on 17 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: Reject page faults from non-fault-mode scratch VMs

Having scratch enabled does not make a VM capable of handling recoverable
page faults. Allowing scratch VMs through the ASID lookup also admits
dma-fence mode VMs.

If such a VM faults on an already valid VMA, the handler reports success
without fixing the fault, causing the GPU to retry indefinitely.

Only allow fault-mode VMs through the ASID lookup. Fault-mode VMs using
scratch remain supported, while faults from 3D VMs are rejected.

(cherry picked from commit bfb24a06405b652d37831f3fb66b71d33a6605de)

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


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

Apply the vendor's patch.

## Is CVE-2026-90064 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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