Skip to main content
VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99630· Medium

Not known to be exploited : upgrade to ce5f2a25bdf6b2bccfc4ffb5e4c5f12e97eeace1 or 2664f497d5e35384736e42fc59e5b9ef27ca791a when convenient.

Data as of 20 Nov 2026, 07:34 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in ce5f2a25bdf6b2bccfc4ffb5e4c5f12e97eeace1, 2664f497d5e35384736e42fc59e5b9ef27ca791a

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade Linux kernel to ce5f2a25bdf6b2bccfc4ffb5e4c5f12e97eeace1 or 2664f497d5e35384736e42fc59e5b9ef27ca791a.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 4cdbba5a16aaf16513b69cc332b1d6f971a44b52, < ce5f2a25bdf6b2bccfc4ffb5e4c5f12e97eeace1
Fixed in
  • ce5f2a25bdf6b2bccfc4ffb5e4c5f12e97eeace1
LinuxLinuxAffected
  • ≥ 4cdbba5a16aaf16513b69cc332b1d6f971a44b52, < 2664f497d5e35384736e42fc59e5b9ef27ca791a
Fixed in
  • 2664f497d5e35384736e42fc59e5b9ef27ca791a
LinuxLinuxAffected
  • =7.2
Fixed in–

Description

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)

References

Community reviews

Loading reviews…