GPU VulnDB

Database/NVIDIA / GPU stack

Linux kernel amdgpu: unvalidated GEM_CREATE domain combinations hit a BUG_ON and panic the node

UnscoredCVE-2026-80541NVIDIA / GPU stackcurated

Impact

AMDGPU_GEM_CREATE checked domain bits against AMDGPU_GEM_DOMAIN_MASK but never validated which combinations make sense. Userspace could combine CPU, GTT or VRAM with DOORBELL, GDS, GWS or OA, so amdgpu_bo_placement_from_domain() builds more placements than AMDGPU_BO_MAX_PLACEMENTS and trips a BUG_ON. A BUG_ON in an ioctl path is an immediate kernel panic, reachable with a single crafted allocation request. On a multi-tenant GPU node this is a one-call denial of service against every job on the box: one tenant's pod takes down the host and everything sharing it, and recovery is a reboot rather than a container restart.

Who can reach it

Local user with access to an amdgpu render node (/dev/dri/renderD*) - i.e. any tenant with a GPU pod. A single ioctl with an invalid domain combination is enough; no authentication or elevated capability required.

What to do

Apply the stable fix, which adds amdgpu_gem_are_domains_valid() and returns -EINVAL for invalid combinations in amdgpu_gem_create_ioctl(). Five stable commits are listed; the record names no fixed release version. Rollout is a patched kernel and a per-node reboot, so drain GPU workloads first. There is no configuration mitigation short of denying tenants direct render-node access.

References

https://nvd.nist.gov/vuln/detail/CVE-2026-80541https://git.kernel.org/stable/c/220aa2589d7321fb68d2e8597862711b5f22ae0bhttps://git.kernel.org/stable/c/493355096e397f9217b41c8574ed2784c7351443https://git.kernel.org/stable/c/584e3d47736fe2e7184ef3fc16b00b41485f96c6

Related entries

All NVIDIA / GPU stack entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.