CVE-2026-46311: drm/amdgpu/userq: fix access to stale wptr mapping
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.09% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2da62dbb4169e758c0b1a9378b39a373bf4fb111, 336a9186f3a4b65bbd865d93936605ac8a1a3991, 6da7b1242da4455b11c24ce667d1cab1a348c8ea.
Low priority for now. Upgrade to Linux Linux 2da62dbb4169e758c0b1a9378b39a373bf4fb111, 336a9186f3a4b65bbd865d93936605ac8a1a3991, 6da7b1242da4455b11c24ce667d1cab1a348c8ea or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/userq: fix access to stale wptr mapping Use drm_exec to take both locks i.e vm root bo and wptr_obj bo to access the mapping data properly. This fixes the security issue of unmap the wptr_obj while a queue creation is in progress and passing other bo at same address. (cherry picked from commit 1fc6c8ab45dbee096469c08c13f6099d57a52d6c)
- Published
- Jun 8, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.0% · 0th percentile
- CWE
- CWE-362
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.0%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.16affected
- 5fb2f7fc21a3668e5794cc0d153641b9719713e1 and later · before 2da62dbb4169e758c0b1a9378b39a373bf4fb111affected · git
- 5fb2f7fc21a3668e5794cc0d153641b9719713e1 and later · before 336a9186f3a4b65bbd865d93936605ac8a1a3991affected · git
- 5fb2f7fc21a3668e5794cc0d153641b9719713e1 and later · before 6da7b1242da4455b11c24ce667d1cab1a348c8eaaffected · git
- before 6.16not affected · semver
- 6.18.57 and later · up to and including 6.18.*not affected · semver
- 7.0.9 and later · up to and including 7.0.*not affected · semver
- 7.1 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.16 and later · before 7.0.9
- linux linux kernel7.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.60.1.el10_2 | 6.12.0-211.60.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-46307Jun 8, 2026 · wifi: ath5k: do not access array OOB33Monitor
- ← EarlierCVE-2026-46309Jun 8, 2026 · drm/xe/uapi: Reject coh_none PAT index for CPU cached memory in madvise28Monitor
- Later →CVE-2026-46312Jun 8, 2026 · media: videobuf2: Set vma_flags in vb2_dma_sg_mmap22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2da62dbb4169e758c0b1a9378b39a373bf4fb111 | Vendor (CNA) |
| Linux Linux | 336a9186f3a4b65bbd865d93936605ac8a1a3991 | Vendor (CNA) |
| Linux Linux | 6da7b1242da4455b11c24ce667d1cab1a348c8ea | Vendor (CNA) |
| almalinux:kernel | 5.14.0-687.52.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel | 6.12.0-211.60.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-687.52.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.60.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-687.52.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.60.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-687.52.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.60.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-687.52.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.60.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-687.52.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.60.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-687.52.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.60.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-687.52.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.60.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-687.52.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.60.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-687.52.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.60.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-687.52.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.60.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-687.52.1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.60.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 7.0.9-1 · Debian:14 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-211.60.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-211.60.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
+11
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.