# CVE-2026-99119: drm/amdgpu/userq: actually validate userq BOs


- **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-99119, GHSA-wrf7-g73g-gr9r, UBUNTU-CVE-2026-99119

## What is CVE-2026-99119?

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

### Official 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)

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


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

Upgrade to a fixed version.

## Is CVE-2026-99119 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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