CVE-2026-74312

vhost/vdpa: validate virtqueue index in mmap and fault paths

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 05:58 AM UTC
Updated: October 16, 2026 at 07:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.8ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9
Vendor states this is fixed in 0f310bac6db9bd3bb1655707d692d9d2a86eeb17 (fixed)
Vendor states this is fixed in 1f5f94c6c6b2e4eaa5b45815509e21d0c6cfa81e (fixed)
Vendor states this is fixed in 2b3f79b90b231a682315fe2191bb71925650e183 (fixed)
Vendor states this is fixed in 32ac9097aa2463fcfc12f61cc4a9ebc3579cba7d (fixed)
Vendor states this is fixed in 4bf5a51963ff816f7443702dc536b9327cf5e550 (fixed)
Vendor states this is fixed in 55a644031e610ea93fbde2702c7b8f267476552f (fixed)
Vendor states this is fixed in 929e4f044621c8cc30b612fb74e1410bef09e41b (fixed)
Vendor states this is fixed in bbba4f92515238d76018e9b75e41b16d83df52c8 (fixed)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 5.8 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card