CVE-2026-80541 — drm/amdgpu: validate GEM_CREATE domain combinations
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)
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 77a2faa55c1a497f4e7e89eabd11830f0e3cb3dd and < 5c73485af7ad9c3ae592db3481f370bc07705391≥ 77a2faa55c1a497f4e7e89eabd11830f0e3cb3dd and < 584e3d47736fe2e7184ef3fc16b00b41485f96c6≥ 77a2faa55c1a497f4e7e89eabd11830f0e3cb3dd and < 66133fc05c3af002f45de8a71b833c026ccbfba6≥ 77a2faa55c1a497f4e7e89eabd11830f0e3cb3dd and < ce5da474c3ddf7cccec5dce6aa4296297dd7caff≥ 77a2faa55c1a497f4e7e89eabd11830f0e3cb3dd and < 493355096e397f9217b41c8574ed2784c7351443≥ 77a2faa55c1a497f4e7e89eabd11830f0e3cb3dd and < 220aa2589d7321fb68d2e8597862711b5f22ae0b≥ 77a2faa55c1a497f4e7e89eabd11830f0e3cb3dd and < 80f0b53860d02577709d69a312a29ca674b9297c≥ 77a2faa55c1a497f4e7e89eabd11830f0e3cb3dd and < 5e9d136ad74df4edec67e502ce267597064d8f86 and 1 moreversion 4.20 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.8
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/5e9d136ad74df4edec67e502ce267597064d8f86
- git.kernel.org/stable/c/5c73485af7ad9c3ae592db3481f370bc07705391
- git.kernel.org/stable/c/66133fc05c3af002f45de8a71b833c026ccbfba6
- git.kernel.org/stable/c/80f0b53860d02577709d69a312a29ca674b9297c
- git.kernel.org/stable/c/493355096e397f9217b41c8574ed2784c7351443
- git.kernel.org/stable/c/ce5da474c3ddf7cccec5dce6aa4296297dd7caff
- git.kernel.org/stable/c/220aa2589d7321fb68d2e8597862711b5f22ae0b
- git.kernel.org/stable/c/584e3d47736fe2e7184ef3fc16b00b41485f96c6
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 11h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 11h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-80541 is "drm/amdgpu: validate GEM_CREATE domain combinations", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.