Skip to main content
VulnerabilityPublished

CVE-2026-99633: Linux kernel · drm/amdgpu: keep the CS user fence BO in GTT

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in b4a1229ab05f0ba7fa1a52032686e32e801fcc04 : update Linux kernel when convenient.

Data as of 20 Nov 2026, 06:04 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in b4a1229ab05f0ba7fa1a52032686e32e801fcc04, 69a46cbe11b6eb15f6d48591a67217ac634ddc3d, 7a56d929dc2304edaa6231e1eb5eb82b7e8b74a9 +4

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 to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • <6.12.118
  • <6.18.64
  • <7.3.5
Fixed in
  • b4a1229ab05f0ba7fa1a52032686e32e801fcc04
  • 69a46cbe11b6eb15f6d48591a67217ac634ddc3d
  • 7a56d929dc2304edaa6231e1eb5eb82b7e8b74a9
  • 7.3.5
  • 6.18.64
  • 6.12.118
  • 2c7bd4568f5d19d63241ccdf930b15e619af7c2b

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: keep the CS user fence BO in GTT The CS ioctl hands the GPU the GART address of the user fence BO, but since the BO keeps its own preferred and allowed domains, it no longer makes sure the BO is in GTT. A user fence in a VRAM BO, which only needs to be a page in size, gets its address from amdgpu_bo_gpu_offset(), which warns about non-contiguous VRAM. On navi31, a CS with a user fence in a 4K VRAM BO, or in one created with AMDGPU_GEM_CREATE_VM_ALWAYS_VALID: WARNING: amdgpu_object.c:1531 at amdgpu_bo_gpu_offset+0x86/0xb0 [amdgpu], CPU#11: cs_gem_checks/18393 RIP: 0010:amdgpu_bo_gpu_offset+0x86/0xb0 [amdgpu] Call Trace: <TASK> amdgpu_cs_parser_bos.isra.0+0x4eb/0x850 [amdgpu] amdgpu_cs_ioctl+0x97e/0x2510 [amdgpu] drm_ioctl_kernel+0xac/0x110 [drm] drm_ioctl+0x2c6/0x5b0 [drm] __x64_sys_ioctl+0xa0/0xf0 do_syscall_64+0xa3/0x4d0 entry_SYSCALL_64_after_hwframe+0x76/0x7e and BOs which can't be in GTT at all, like GWS or OA ones of a page in size, pass the checks as well. Only take BOs which can't be anywhere else than in GTT as user fence, which the CS then validates there along with its other BOs. While at it, detect userptrs with amdgpu_ttm_tt_is_userptr(); amdgpu_ttm_tt_get_usermm() returns NULL once the task which created the userptr is gone. v2: only take BOs which can only be in GTT instead of special casing the user fence BO in the validation, use amdgpu_ttm_tt_is_userptr() (Christian) (cherry picked from commit f16989def9561d04d0f2e77216f5319112d29bf1)

References

Community reviews

Loading reviews…