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 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)
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 1ea863fd736eed8217a0b7bc5d0bd0de6b267b80; < b4a1229ab05f0ba7fa1a52032686e32e801fcc04 (affected, git) ≥ 1ea863fd736eed8217a0b7bc5d0bd0de6b267b80; < 69a46cbe11b6eb15f6d48591a67217ac634ddc3d (affected, git) ≥ 1ea863fd736eed8217a0b7bc5d0bd0de6b267b80; < 2c7bd4568f5d19d63241ccdf930b15e619af7c2b (affected, git) ≥ 1ea863fd736eed8217a0b7bc5d0bd0de6b267b80; < 7a56d929dc2304edaa6231e1eb5eb82b7e8b74a9 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
4.6 (affected) ≥ 0; < 4.6 (unaffected, semver) ≥ 6.12.118; ≤ 6.12.* (unaffected, semver) ≥ 6.18.64; ≤ 6.18.* (unaffected, semver) ≥ 7.3.5; ≤ 7.3.* (unaffected, semver) ≥ 7.4-rc2; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/b4a1229ab05f0ba7fa1a52032686e32e801fcc04CNA: Linux
- https://git.kernel.org/stable/c/69a46cbe11b6eb15f6d48591a67217ac634ddc3dCNA: Linux
- https://git.kernel.org/stable/c/2c7bd4568f5d19d63241ccdf930b15e619af7c2bCNA: Linux
- https://git.kernel.org/stable/c/7a56d929dc2304edaa6231e1eb5eb82b7e8b74a9CNA: Linux
- https://git.kernel.org/stable/c/2c7bd4568f5d19d63241ccdf930b15e619af7c2b416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/69a46cbe11b6eb15f6d48591a67217ac634ddc3d416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/7a56d929dc2304edaa6231e1eb5eb82b7e8b74a9416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/b4a1229ab05f0ba7fa1a52032686e32e801fcc04416baaa9-dc9f-4396-8d5f-8c081fb06d67
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.