CVE-2026-99633: drm/amdgpu: keep the CS user fence BO in GTT
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 amdgpubogpuoffset(), which warns about non-contiguous VRAM. On navi31, a CS with a user fence in a 4K VRAM BO, or in one created with AMDGPUGEMCREATEVMALWAYSVALID:
WARNING: amdgpuobject.c:1531 at amdgpubogpuoffset+0x86/0xb0 [amdgpu], CPU#11: csgemchecks/18393 RIP: 0010:amdgpubogpuoffset+0x86/0xb0 [amdgpu] Call Trace: <TASK> amdgpucsparserbos.isra.0+0x4eb/0x850 [amdgpu] amdgpucsioctl+0x97e/0x2510 [amdgpu] drmioctlkernel+0xac/0x110 [drm] drmioctl+0x2c6/0x5b0 [drm] x64sysioctl+0xa0/0xf0 dosyscall64+0xa3/0x4d0 entrySYSCALL64afterhwframe+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 amdgputtmttisuserptr(); amdgputtmttgetusermm() 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 amdgputtmttisuserptr() (Christian)
(cherry picked from commit f16989def9561d04d0f2e77216f5319112d29bf1)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.5-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Patch f16989def9561d04d0f2e77216f5319112d29bf1
Event History
Frequently Asked Questions
What conditions are needed to trigger the warning?
A command submission must use a user-fence buffer object that is not constrained to GTT. Reported triggering cases include a 4K VRAM buffer object on Navi31 and a buffer object created with AMDGPU_GEM_CREATE_VM_ALWAYS_VALID.
Are buffer objects that cannot reside in GTT affected?
Yes. Page-sized GWS or OA buffer objects, which cannot be placed in GTT, could pass the prior checks when used as user fences.
What behavior does the fix enforce?
The fix accepts only user-fence buffer objects that cannot be placed anywhere other than GTT. The command submission then validates the user-fence buffer object in GTT with its other buffer objects.