# CVE-2026-72359: drm/xe: fix NPD in bo_meminfo()

> A local attacker can trigger a kernel crash by querying memory stats for a purged buffer object in the Intel Xe GPU driver.

- **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:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-72359, GHSA-r35w-2gcj-cx97, UBUNTU-CVE-2026-72359

## What is CVE-2026-72359?

CVE-2026-72359 is a vulnerability in Linux, published on 15 Aug 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 NPD in bo_meminfo()

When a buffer object is purged, its ttm.resource is set to NULL via the
TTM pipeline gutting flow. However, the BO remains in the client's
object list until userspace explicitly closes the GEM handle. If memory
stats are queried during this time, accessing bo->ttm.resource->mem_type
will result in a NULL pointer dereference.

Fix this by safely skipping purged BOs in bo_meminfo, as they no longer
consume any memory.

User is getting NPD on device resume, and possible theory is that in
bo_move(), if we need to evict something to SYSTEM to save the CCS state,
but the BO is marked as dontneed, this won't trigger a move but will
nuke the pages, leaving us with a NULL bo resource. And the meminfo()
doesn't look ready to handle a NULL resource.

v2 (Sashiko):
 - There could potentially be other cases where we might end up with a
   NULL resource, so make this a general NULL check for now.

(cherry picked from commit c9a8e7daa0afe3161111e27fd92176e608c7f186)

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


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

Apply the vendor's patch.

## Is CVE-2026-72359 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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