Strix
58.1K

CVE-2026-74312

HIGHCVSS 7.8/10EPSS 0.18%

Last modified

CVE-2026-74312 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.18% chance of exploitation in the next 30 days.

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.

Metrics

CVSS 3.1
7.8/10

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Probability
0.18%

7.4th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9, < 0f310bac6db9bd3bb1655707d692d9d2a86eeb17; >= ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9, < 4bf5a51963ff816f7443702dc536b9327cf5e550; >= ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9, < 55a644031e610ea93fbde2702c7b8f267476552f; >= ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9, < 2b3f79b90b231a682315fe2191bb71925650e183; >= ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9, < bbba4f92515238d76018e9b75e41b16d83df52c8; >= ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9, < 1f5f94c6c6b2e4eaa5b45815509e21d0c6cfa81e; >= ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9, < 32ac9097aa2463fcfc12f61cc4a9ebc3579cba7d; >= ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9, < 929e4f044621c8cc30b612fb74e1410bef09e41b
LinuxLinux5.8

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-74312?
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.
How severe is CVE-2026-74312?
CVE-2026-74312 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.
How do I fix CVE-2026-74312?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-74312?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST