VulnerabilityPublished 28 Oct 2026

CVE-2026-99119: Linux kernel · drm/amdgpu/userq: actually validate userq BOs

Affects Linux kernelSource CVE Database V5

Not known to be exploited : upgrade to d1d6b859e89dd274cd0fae77503cdf91be8310c0 or 32d0771ef4ca69c30a1db3aefa34dd177cd2a047 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 d1d6b859e89dd274cd0fae77503cdf91be8310c0, 32d0771ef4ca69c30a1db3aefa34dd177cd2a047

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 d1d6b859e89dd274cd0fae77503cdf91be8310c0 or 32d0771ef4ca69c30a1db3aefa34dd177cd2a047.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 4cdbba5a16aaf16513b69cc332b1d6f971a44b52, < d1d6b859e89dd274cd0fae77503cdf91be8310c0	Fixed in d1d6b859e89dd274cd0fae77503cdf91be8310c0
LinuxLinux	Affected ≥ 4cdbba5a16aaf16513b69cc332b1d6f971a44b52, < 32d0771ef4ca69c30a1db3aefa34dd177cd2a047	Fixed in 32d0771ef4ca69c30a1db3aefa34dd177cd2a047
LinuxLinux	Affected =7.2	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/userq: actually validate userq BOs This was supposed to loop over the individual evicted list, as the kernel and always_valid evicted lists were already handled in amdgpu_vm_validate. Without this, BOs that were created and evicted before a userq was made would never end up in an eviction fence rearm. Also add the missing ref to the BO before drm_exec locks and refs it. (cherry picked from commit 18decfc9e8cc0fa70b6de9944cc27a37729edfbd)

References

Community reviews

Loading reviews…