# CVE-2026-99145: drm/xe: Don't transfer shrinker pages for pinned bos on purgeable state change


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-99145, GHSA-f7m7-cgc5-xpx5, UBUNTU-CVE-2026-99145

## What is CVE-2026-99145?

CVE-2026-99145 is a vulnerability in Linux, published on 28 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

drm/xe: Don't transfer shrinker pages for pinned bos on purgeable state change

Pinned bos have their pages removed from the shrinker's shrinkable /
purgeable counts on pin, and added back on unpin according to the
bo's purgeable state at that time.

However, xe_bo_set_purgeable_shrinker() unconditionally transfers
pages between the shrinkable and purgeable counts. If the purgeable
state of a pinned bo changes, for example by userspace madvising
DONTNEED on a VMA of a bo that is also pinned as a scanout buffer,
this underflows one count and, after unpin, leaves the other one
permanently inflated.

Only update the purgeable flag for pinned bos, and leave the page
accounting to unpin.

(cherry picked from commit afe6bc012034123fd838328668e609bf57e46bd3)

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


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

Upgrade to a fixed version.

## Is CVE-2026-99145 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-99145 is a vulnerability in Linux, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99145 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-99145/ (Markdown: https://insights.sbomify.com/CVE-2026-99145/index.md)
```

## Sources

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

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