Look up another CVE · open CVE-2026-80541 in the interactive tracker
CVE-2026-80541
drm/amdgpu: validate GEM_CREATE domain combinations
Published 2026-08-26 (2 months ago) by the Linux kernel CNA. Subsystem drivers/gpu. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-80541 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixedDLA-4777-1 · 2026-09-08 · text | 6.1.187-1 | Update the kernel and reboot. DLA-4777-1 shipped the fix on 2026-09-08, in 6.1.187-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.105-1 | Update the kernel and reboot. Fixed in 6.12.105-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.10-1 | Update the kernel and reboot. Fixed in 7.1.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.10-1 | Update the kernel and reboot. Fixed in 7.1.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4788-1 · 2026-09-19 · text | 6.12.107-1~deb12u1 | Update the kernel and reboot. DLA-4788-1 shipped the fix on 2026-09-19, in 6.12.107-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
AMDGPU_GEM_CREATE checked domain bits against AMDGPU_GEM_DOMAIN_MASK, but did not validate domain combinations. Userspace could combine CPU|GTT|VRAM with DOORBELL, GDS, GWS, or OA, making amdgpu_bo_placement_from_domain() exceed AMDGPU_BO_MAX_PLACEMENTS and hit BUG_ON(). Allow combinations only within CPU/GTT/VRAM, and require non-CPU/GTT/ VRAM domains to be specified one at a time. Return -EINVAL for invalid combinations in amdgpu_gem_create_ioctl(). v2: Rename helper from amdgpu_gem_domain_valid() to amdgpu_gem_are_domains_valid() (Christian) (cherry picked from commit db39852d0c39843cb02048dfb47e4b8c703e9080)
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
- What this is
- RADEON and AMDGPU DRM DRIVERSMAINTAINERS section matched on drivers/gpu/drm/amd/ · amd-gfx@lists.freedesktop.org · Supported
- Kernel module
- amdgpu
Check it on the machine
grep -w CONFIG_DRM_AMDGPU /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w amdgpuPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookwormMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp
- trixieMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, s390x/s390x
- forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, s390x/s390x
- bookworm · linux-6.12Mnot built on amd64/cloud-amd64, arm64/cloud-arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp
- M
- a module where it is built at all; some flavours do not build it
- Build switch
- CONFIG_DRM_AMDGPU
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-26 (2 months ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.13%, higher than 2.3% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/gpu
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 4.20 | 5.10.266 | 5c73485af7ad |
| 4.20 | 5.15.217 | 584e3d47736f |
| 4.20 | 6.1.184 | 66133fc05c3a |
| 4.20 | 6.6.153 | ce5da474c3dd |
| 4.20 | 6.12.105 | 493355096e39 |
| 4.20 | 6.18.46 | 220aa2589d73 |
| 4.20 | 7.1.10 | 80f0b53860d0 |
| 4.20 | 7.2 | 5e9d136ad74d |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4788-1 | 2026-09-19 | bookworm 6.12.107-1~deb12u1 | tracker |
| DLA-4777-1 | 2026-09-08 | bookworm 6.1.187-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- The bug is reached only via DRM_IOCTL_AMDGPU_GEM_CREATE on a local amdgpu render node (/dev/dri/renderD*); userspace passes crafted domain flags into amdgpu_gem_create_ioctl(), which calls amdgpu_bo_placement_from_domain() during amdgpu_bo_create(). There is no network, adjacent-radio, or physical-access path to this code.
- AC:LAttack complexity, low
- Triggering is a single deterministic ioctl with an invalid domain bitmask (e.g. CPU|GTT|VRAM|DOORBELL); the attacker fully controls the domains field and needs no race, special memory layout, or victim state. Invalid combinations reliably exceed AMDGPU_BO_MAX_PLACEMENTS (3) and hit BUG_ON() on every attempt.
- PR:LPrivileges required, low
- AMDGPU_GEM_CREATE is registered with DRM_AUTH|DRM_RENDER_ALLOW, so any local unprivileged user who can open the render node (default on desktops, ChromeOS, Steam Deck, and cloud GPU tenants via render/video group or ACL) can invoke it without real root or init-namespace capabilities.
- UI:NUser interaction, none
- The attacking process performs the GEM_CREATE ioctl itself; no other user must mount a filesystem, open a file, click a link, or take any other action for the invalid domain combination to reach amdgpu_bo_placement_from_domain() and panic the kernel.
- S:UScope, unchanged
- Impact is confined to host-kernel memory corruption and panic within the amdgpu/TTM driver; it does not cross a VM, IOMMU, or sandbox security boundary, and is standard local kernel privilege-escalation/DoS scope rather than a guest-to-host escape.
- C:HConfidentiality impact, high
- Before BUG_ON(), amdgpu_bo_placement_from_domain() writes past the fixed placements[AMDGPU_BO_MAX_PLACEMENTS] array into adjacent amdgpu_bo fields (including struct ttm_placement) with attacker-influenced mem_type and flag values; this out-of-bounds write is memory corruption that could be leveraged for kernel info disclosure.
- I:HIntegrity impact, high
- The same out-of-bounds placement writes corrupt adjacent kernel heap objects in the amdgpu_bo allocation with partially attacker-controlled ttm_place contents; out-of-bounds writes into kernel structures are classed as high integrity impact and could enable further heap corruption or control-flow hijacking.
- A:HAvailability impact, high
- Once placement count exceeds three the kernel hits BUG_ON(c > AMDGPU_BO_MAX_PLACEMENTS), causing an oops or panic; an unprivileged GPU client on shared AMD hardware (multi-user workstations or cloud GPU nodes) can repeatedly crash the entire host, denying service to all co-tenants.