# CVE-2026-99630: drm/amdgpu/userq: validate the moved individual BOs on restore

Status: published. Published: 2026-11-20. Updated: 2026-11-22.

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

drm/amdgpu/userq: validate the moved individual BOs on restore

An individual BO of a user queue VM, i.e. one which doesn't share the
root reservation, goes to the individual needs_update list when it is
evicted. The user queue restore looked at vm->invalidated for them, which
the VM state machine rework turned into the always_valid evicted list and
commit 18decfc9e8cc ("drm/amdgpu/userq: actually validate userq BOs")
into the individual evicted one. That list only holds imported DMA-bufs of
compute VMs though, so for a user queue VM nothing is validated.

The restore then neither locks such a BO nor moves it back. Its PTEs are
updated to wherever it is now, cleared if it went to system memory, and
it doesn't get the new eviction fence, so it can move again under the
running queue.

On navi48, once the BOs of an SDMA user queue are evicted from GTT
(debugfs amdgpu_evict_gtt) the queue faults on its ring and rptr:

  amdgpu 0000:03:00.0:   in page starting at address 0x0000000100000000 from client 10
  amdgpu 0000:03:00.0: 	 Faulty UTCL2 client ID: SDMA0 (0xd)
  amdgpu 0000:03:00.0:   in page starting at address 0x0000000100101000 from client 10

Validate the BOs on the individual needs_update list like before.

(cherry picked from commit eb0d94765d4be18d41e93ad09947dd9cc06ed31a)

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 4cdbba5a16aaf16513b69cc332b1d6f971a44b52; < 2664f497d5e35384736e42fc59e5b9ef27ca791a (affected, git); ≥ 4cdbba5a16aaf16513b69cc332b1d6f971a44b52; < ce5f2a25bdf6b2bccfc4ffb5e4c5f12e97eeace1 (affected, git). Source: CNA: Linux
- Linux / Linux: 7.2 (affected); ≥ 0; < 7.2 (unaffected, semver); ≥ 7.3.5; ≤ 7.3.* (unaffected, semver); ≥ 7.4-rc2; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CVSS 3.1: 7 (high); CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H; source: CNA: Linux

- CVSS 3.1: 7 (high); CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H; source: NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

- CISA KEV: No listing in collected sources

- EPSS: 0.16% as of 2026-11-21; percentile 4.72%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/2664f497d5e35384736e42fc59e5b9ef27ca791a (CNA: Linux)

- https://git.kernel.org/stable/c/ce5f2a25bdf6b2bccfc4ffb5e4c5f12e97eeace1 (CNA: Linux)

- https://git.kernel.org/stable/c/2664f497d5e35384736e42fc59e5b9ef27ca791a (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/ce5f2a25bdf6b2bccfc4ffb5e4c5f12e97eeace1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99630; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99630; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99630; retrieved 2026-11-22; source updated Not reported

Revision: ab20e6a700ccc99487abf7cd8ffd82caac66e5630d00cfd3295f0ca3cdfb9251

Canonical: https://y2.dev/cve/CVE-2026-99630

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.