CVE-2026-74580vhost: reset the vring metadata cache on vring reconfiguration
- 8.8HighCVSS base score
- 0.41%Exploitation in 30 daysEPSS · top 64% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- YesPublic exploitsa reference or SSVC says so
Description
In the Linux kernel, the following vulnerability has been resolved: vhost: reset the vring metadata cache on vring reconfiguration vq->meta_iotlb[] caches the vhost_iotlb_map that backs each vring metadata region, and iotlb_access_ok() returns early on a cache hit, taking the hit as proof that the region has already been validated: if (vhost_vq_meta_fetch(vq, addr, len, type)) return true; The cache is reset on VHOST_IOTLB_UPDATE and VHOST_IOTLB_INVALIDATE, on device IOTLB (re)initialisation and on vq reset, but not when VHOST_SET_VRING_ADDR replaces vq->desc, vq->avail and vq->used, nor when VHOST_SET_VRING_NUM changes the region sizes. With a device IOTLB attached both ioctls are accepted while the vq is live, and neither validates the addresses at ioctl time: vq_access_ok() and vq_log_used_access_ok() return true early because the addresses are GIOVAs, deferring validation to prefetch time. Once the cache has been populated that deferred validation no longer runs -- vq_meta_prefetch() hits the stale entry and returns true -- and vhost_vq_meta_fetch() keeps translating through the old mapping as map->addr + addr - map->start for an address the mapping no longer covers. vhost_copy_to_user() and vhost_copy_from_user() consume the result with __copy_to_user() and __copy_from_user(), which do not check it either, so a subsequent used ring update or descriptor fetch accesses memory outside the region the IOTLB actually maps. Reset the metadata cache whenever the vring is reconfigured, so the new addresses are pushed back through iotlb_access_ok()'s slow path.
Public exploit
An exploit or proof of concept is public: anyone can try it against an unpatched system. A reference of the record is tagged as an exploit. CISA's SSVC rates its exploitation: a proof of concept is public.
Show the exploits1
References tagged exploit1 reference
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 2 months later
· 2 months 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High8.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.41% · top 64% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: poc · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.
Affected products
- affected f889491380582b4ba2981cf0b0d7d6a40fb30ab7 – < 5224bd37e37d36076a550d99b2aebba33939fd95
- affected f889491380582b4ba2981cf0b0d7d6a40fb30ab7 – < 54617e9119be2eb728ecdd8d977b99c99d4c498a
- affected f889491380582b4ba2981cf0b0d7d6a40fb30ab7 – < 13fa6f32a56a386a82bd7451644c494beed034af
- affected f889491380582b4ba2981cf0b0d7d6a40fb30ab7 – < cf363a7a02ce132ef1f58084fdb13e1a3b7da7e7
- affected f889491380582b4ba2981cf0b0d7d6a40fb30ab7 – < 6fa3e9b1fe856259555a7e22f3f3082e7827fd9b
- affected f889491380582b4ba2981cf0b0d7d6a40fb30ab7 – < f1e21108e3ddfcce62f6cad4ebd7b5674543c9e6
- affected f889491380582b4ba2981cf0b0d7d6a40fb30ab7 – < b70ebe0bba254e093dd5fd4c0c170941ce83eb85
- affected f889491380582b4ba2981cf0b0d7d6a40fb30ab7 – < de845981da67a6b049080c87e605130b0c30adc5
- affected 4.11
- unaffected < 4.11
- unaffected 5.10.265 – ≤ 5.10.*
- unaffected 5.15.216 – ≤ 5.15.*
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.152 – ≤ 6.6.*
- unaffected 6.12.104 – ≤ 6.12.*
- unaffected 6.18.45 – ≤ 6.18.*
- unaffected 7.1.9 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References10
- https://git.kernel.org/stable/c/5224bd37e37d36076a550d99b2aebba33939fd95 (opens in a new tab)
- https://git.kernel.org/stable/c/54617e9119be2eb728ecdd8d977b99c99d4c498a (opens in a new tab)
- https://git.kernel.org/stable/c/13fa6f32a56a386a82bd7451644c494beed034af (opens in a new tab)
- https://git.kernel.org/stable/c/cf363a7a02ce132ef1f58084fdb13e1a3b7da7e7 (opens in a new tab)
- https://git.kernel.org/stable/c/6fa3e9b1fe856259555a7e22f3f3082e7827fd9b (opens in a new tab)
- https://git.kernel.org/stable/c/f1e21108e3ddfcce62f6cad4ebd7b5674543c9e6 (opens in a new tab)
- https://git.kernel.org/stable/c/b70ebe0bba254e093dd5fd4c0c170941ce83eb85 (opens in a new tab)
- https://git.kernel.org/stable/c/de845981da67a6b049080c87e605130b0c30adc5 (opens in a new tab)
- http://www.openwall.com/lists/oss-security/2026/10/14/2 (opens in a new tab)
- https://github.com/YounesHfa/CVE-2026-74580 (opens in a new tab)exploit
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-64002 (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-74580)Record last updated .