# CVE-2026-80541: drm/amdgpu: validate GEM_CREATE domain combinations

> A local attacker can trigger a kernel BUG_ON crash by passing invalid GPU memory domain combinations to the AMDGPU driver.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** AZL-97752, BELL-CVE-2026-80541, DEBIAN-CVE-2026-80541, GHSA-6pqc-pjg3-fqrx, UBUNTU-CVE-2026-80541

## What is CVE-2026-80541?

CVE-2026-80541 is a high-severity denial of service vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: validate GEM_CREATE domain combinations

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)

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


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

Apply the vendor's patch.

## Is CVE-2026-80541 being exploited?

There is no known exploitation of CVE-2026-80541 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80541 and fix it if it is affected.

What it is: CVE-2026-80541 is a high-severity denial of service vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80541 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80541/ (Markdown: https://insights.sbomify.com/CVE-2026-80541/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80541
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80541
- OSV: https://osv.dev/vulnerability/CVE-2026-80541

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80541/
Summaries are generated and may contain mistakes; the official description above is the record.