Linux
vhost/vdpa: validate virtqueue index in mmap and fault paths
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9, < 0f310bac6db9bd3bb1655707d692d9d2a86eeb17
- >= ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9, < 4bf5a51963ff816f7443702dc536b9327cf5e550
- >= ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9, < 55a644031e610ea93fbde2702c7b8f267476552f
- >= ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9, < 2b3f79b90b231a682315fe2191bb71925650e183
- >= ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9, < bbba4f92515238d76018e9b75e41b16d83df52c8
- >= ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9, < 1f5f94c6c6b2e4eaa5b45815509e21d0c6cfa81e
- >= ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9, < 32ac9097aa2463fcfc12f61cc4a9ebc3579cba7d
- >= ddd89d0a059d8e9740c75a97e0efe9bf07ee51f9, < 929e4f044621c8cc30b612fb74e1410bef09e41b
Fixed in 0f310bac6db9bd3bb1655707d692d9d2a86eeb17, 4bf5a51963ff816f7443702dc536b9327cf5e550, 55a644031e610ea93fbde2702c7b8f267476552f, 2b3f79b90b231a682315fe2191bb71925650e183, bbba4f92515238d76018e9b75e41b16d83df52c8, 1f5f94c6c6b2e4eaa5b45815509e21d0c6cfa81e, 32ac9097aa2463fcfc12f61cc4a9ebc3579cba7d, 929e4f044621c8cc30b612fb74e1410bef09e41b
- 5.8
Fixed in 0, 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5, 7.2
Mitigation
Upgrade Linux to 0f310bac6db9bd3bb1655707d692d9d2a86eeb17 or 4bf5a51963ff816f7443702dc536b9327cf5e550 or 55a644031e610ea93fbde2702c7b8f267476552f or 2b3f79b90b231a682315fe2191bb71925650e183 or bbba4f92515238d76018e9b75e41b16d83df52c8 or 1f5f94c6c6b2e4eaa5b45815509e21d0c6cfa81e or 32ac9097aa2463fcfc12f61cc4a9ebc3579cba7d or 929e4f044621c8cc30b612fb74e1410bef09e41b or later.
Upgrade Linux to 0 or 5.10.261 or 5.15.212 or 6.1.178 or 6.6.145 or 6.12.97 or 6.18.40 or 7.1.5 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.