vhost/vdpa: validate virtqueue index in mmap and fault paths
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9 · fixed in 0f310bac6db9bd3bb1655707d692d9d2a86eeb17; From ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9 · fixed in 4bf5a51963ff816f7443702dc536b9327cf5e550; From ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9 · fixed in 55a644031e610ea93fbde2702c7b8f267476552f; From ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9 · fixed in 2b3f79b90b231a682315fe2191bb71925650e183; From ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9 · fixed in bbba4f92515238d76018e9b75e41b16d83df52c8; From ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9 · fixed in 1f5f94c6c6b2e4eaa5b45815509e21d0c6cfa81e; From ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9 · fixed in 32ac9097aa2463fcfc12f61cc4a9ebc3579cba7d; From ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9 · fixed in 929e4f044621c8cc30b612fb74e1410bef09e41b
- Linux Linux
5.8
- KernelLinux
From 5.8.0 · fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.97; From 6.13.0 · fixed in 6.18.40; From 6.19.0 · fixed in 7.1.5
References 8
git.kernel.org
- stable/c/0f310bac6db9bd3bb1655707d692d9d2a86eeb17
- stable/c/4bf5a51963ff816f7443702dc536b9327cf5e550
- stable/c/55a644031e610ea93fbde2702c7b8f267476552f
- stable/c/2b3f79b90b231a682315fe2191bb71925650e183
- stable/c/bbba4f92515238d76018e9b75e41b16d83df52c8
- stable/c/1f5f94c6c6b2e4eaa5b45815509e21d0c6cfa81e
- stable/c/32ac9097aa2463fcfc12f61cc4a9ebc3579cba7d
- stable/c/929e4f044621c8cc30b612fb74e1410bef09e41b