CVE-2026-97994vhost/vdpa: reject VRING_NUM larger than device max
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: vhost/vdpa: reject VRING_NUM larger than device max vhost_vring_set_num() accepts any non-zero power-of-two queue size that fits in 16 bits. vhost-vdpa then passes that value to set_vq_num() without comparing it with get_vq_num_max(). A process with access to /dev/vhost-vdpa-* can therefore configure a queue larger than the device advertises. With vdpa_sim, the worker can walk descriptors beyond the mapped descriptor ring. KASAN reports a 16-byte out-of-bounds read, corresponding to one vring_desc, in the vringh IOTLB path: BUG: KASAN: out-of-bounds in _copy_from_iter Read of size 16 copy_from_iotlb copydesc_iotlb vringh_getdesc_iotlb vdpasim_net_work Cache get_vq_num_max() immediately after reset. Some backends derive it from writable queue-size state, so querying it after SET_NUM may return the current size instead of the device capability. Invalidate the cached value before reset so a failed reset leaves SET_NUM disabled. For VHOST_SET_VRING_NUM, copy the complete vring state once and use the same index and size for validation, vq->num, and set_vq_num(). This ensures that validation and use operate on the same copied values.
Timeline
ID reserved
By Linux
Published
- 24 days later
· 24 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 4c8cf31885f69e86be0b5b9e6677a26797365e1d – < 4875c65ca53797a0a402fe2bb54d1b12f28b3cda
- affected 4c8cf31885f69e86be0b5b9e6677a26797365e1d – < 1d09201d81b7d3e276860cc7b7dbf6c6cbe8e9b4
- affected 4c8cf31885f69e86be0b5b9e6677a26797365e1d – < 68232102f20fc961327fb9e0f605a7eaadf030a9
- affected 4c8cf31885f69e86be0b5b9e6677a26797365e1d – < 59522639a7d71cff4e20d594d0b9ea30dd0c77e0
- affected 4c8cf31885f69e86be0b5b9e6677a26797365e1d – < ccb1dc7c527f8c925925cf92afc76ae590dac311
- affected 5.7
- unaffected < 5.7
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2.7 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/4875c65ca53797a0a402fe2bb54d1b12f28b3cda (opens in a new tab)
- https://git.kernel.org/stable/c/1d09201d81b7d3e276860cc7b7dbf6c6cbe8e9b4 (opens in a new tab)
- https://git.kernel.org/stable/c/68232102f20fc961327fb9e0f605a7eaadf030a9 (opens in a new tab)
- https://git.kernel.org/stable/c/59522639a7d71cff4e20d594d0b9ea30dd0c77e0 (opens in a new tab)
- https://git.kernel.org/stable/c/ccb1dc7c527f8c925925cf92afc76ae590dac311 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86648 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-97994)Record last updated .