CVE-2026-74312: vhost/vdpa: validate virtqueue index in mmap and fault paths
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.12% (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 0f310bac6db9bd3bb1655707d692d9d2a86eeb17, 1f5f94c6c6b2e4eaa5b45815509e21d0c6cfa81e, 2b3f79b90b231a682315fe2191bb71925650e183.
Low priority for now. Upgrade to Linux Linux 0f310bac6db9bd3bb1655707d692d9d2a86eeb17, 1f5f94c6c6b2e4eaa5b45815509e21d0c6cfa81e, 2b3f79b90b231a682315fe2191bb71925650e183 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: vhost/vdpa: validate virtqueue index in mmap and fault paths vhost_vdpa_mmap() and vhost_vdpa_fault() use vma->vm_pgoff as a virtqueue index for get_vq_notification(), but they do not validate that the index is smaller than v->nvqs. The ioctl path already performs both a bounds check and array_index_nospec(), but the mmap/fault path only checks that the index fits in u16. This allows an out-of-range queue index to reach driver-specific get_vq_notification() callbacks. Fix this by extracting a unified vhost_vdpa_get_vq_notification() helper that validates the queue index against v->nvqs and applies array_index_nospec() before calling the driver callback. Both the mmap and fault paths use this helper, and the bounds checking is consolidated into a single location. From source inspection, the most defensible impact is out-of-bounds access in the callback path, potentially leading to invalid PFN remaps and crash/DoS.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
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.1%
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.
—
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
- 5.8affected
- ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9 and later · before 0f310bac6db9bd3bb1655707d692d9d2a86eeb17affected · git
- ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9 and later · before 4bf5a51963ff816f7443702dc536b9327cf5e550affected · git
- ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9 and later · before 55a644031e610ea93fbde2702c7b8f267476552faffected · git
- ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9 and later · before 2b3f79b90b231a682315fe2191bb71925650e183affected · git
- ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9 and later · before bbba4f92515238d76018e9b75e41b16d83df52c8affected · git
- ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9 and later · before 1f5f94c6c6b2e4eaa5b45815509e21d0c6cfa81eaffected · git
- ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9 and later · before 32ac9097aa2463fcfc12f61cc4a9ebc3579cba7daffected · git
- ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9 and later · before 929e4f044621c8cc30b612fb74e1410bef09e41baffected · git
- before 5.8not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74308Aug 15, 2026 · ext4: fix kernel BUG in ext4_write_inline_data_end0Monitor
- ← EarlierCVE-2026-74310Aug 15, 2026 · vhost/net: complete zerocopy ubufs only once37Monitor
- Later →CVE-2026-74313Aug 15, 2026 · vduse: hold vduse_lock across IDR lookup in open path35Monitor
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 | 0f310bac6db9bd3bb1655707d692d9d2a86eeb17 | Vendor (CNA) |
| Linux Linux | 1f5f94c6c6b2e4eaa5b45815509e21d0c6cfa81e | Vendor (CNA) |
| Linux Linux | 2b3f79b90b231a682315fe2191bb71925650e183 | Vendor (CNA) |
| Linux Linux | 32ac9097aa2463fcfc12f61cc4a9ebc3579cba7d | Vendor (CNA) |
| Linux Linux | 4bf5a51963ff816f7443702dc536b9327cf5e550 | Vendor (CNA) |
| Linux Linux | 55a644031e610ea93fbde2702c7b8f267476552f | Vendor (CNA) |
| Linux Linux | 929e4f044621c8cc30b612fb74e1410bef09e41b | Vendor (CNA) |
| Linux Linux | bbba4f92515238d76018e9b75e41b16d83df52c8 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: 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)
—
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1f5f94c6c6b2e4eaa5b45815509e21d0c6cfa81e
- git.kernel.org/stable/c/2b3f79b90b231a682315fe2191bb71925650e183
- git.kernel.org/stable/c/32ac9097aa2463fcfc12f61cc4a9ebc3579cba7d
- git.kernel.org/stable/c/4bf5a51963ff816f7443702dc536b9327cf5e550
- git.kernel.org/stable/c/55a644031e610ea93fbde2702c7b8f267476552f
- git.kernel.org/stable/c/929e4f044621c8cc30b612fb74e1410bef09e41b
- git.kernel.org/stable/c/bbba4f92515238d76018e9b75e41b16d83df52c8
Vendor advisories and official records. Exploit/PoC links are deliberately left out.