# CVE-2025-40086: drm/xe: Don't allow evicting of BOs in same VM in array of VM binds

> A local attacker can trigger a NULL pointer dereference in the Linux kernel's Xe GPU driver, causing a system crash.

- **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:** 30 Oct 2025
- **Updated:** 21 Oct 2026
- **Also known as:** BELL-CVE-2025-40086, DEBIAN-CVE-2025-40086, GHSA-j8q5-7w54-24xj, ROOT-OS-DEBIAN-13-CVE-2025-40086, ROOT-OS-UBUNTU-2404-CVE-2025-40086, UBUNTU-CVE-2025-40086

## What is CVE-2025-40086?

CVE-2025-40086 is a vulnerability in Linux, published on 30 Oct 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: Don't allow evicting of BOs in same VM in array of VM binds

An array of VM binds can potentially evict other buffer objects (BOs)
within the same VM under certain conditions, which may lead to NULL
pointer dereferences later in the bind pipeline. To prevent this, clear
the allow_res_evict flag in the xe_bo_validate call.

v2:
 - Invert polarity of no_res_evict (Thomas)
 - Add comment in code explaining issue (Thomas)

(cherry picked from commit 8b9ba8d6d95fe75fed6b0480bb03da4b321bea08)

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


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

Apply the vendor's patch.

## Is CVE-2025-40086 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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