VulnerabilityPublished 28 Oct 2026

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

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to ffbfd3f98f4393e91dffce3a46ccb7cf5329cf2f or 135e998dd1e66b8854db7bd356b6563baf8b9d51 when convenient.

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in ffbfd3f98f4393e91dffce3a46ccb7cf5329cf2f, 135e998dd1e66b8854db7bd356b6563baf8b9d51

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to ffbfd3f98f4393e91dffce3a46ccb7cf5329cf2f or 135e998dd1e66b8854db7bd356b6563baf8b9d51.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 536a2ead3a8f2048643da3e8340a4d73fdf71903, < ffbfd3f98f4393e91dffce3a46ccb7cf5329cf2f	Fixed in ffbfd3f98f4393e91dffce3a46ccb7cf5329cf2f
LinuxLinux	Affected ≥ 536a2ead3a8f2048643da3e8340a4d73fdf71903, < 135e998dd1e66b8854db7bd356b6563baf8b9d51	Fixed in 135e998dd1e66b8854db7bd356b6563baf8b9d51
LinuxLinux	Affected =7.1	Fixed in–

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)

References

Community reviews

Loading reviews…