PoC Monitor
← All CVEs
CVE-2026-74580published 21 Aug 2026 16:31 UTCData: JSON · API

Linux

vhost: reset the vring metadata cache on vring reconfiguration

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.

First public PoC 54 daysafter publication · 14 Oct 2026
Public PoCs22 on GitHub
CVSS8.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= f889491380582b4ba2981cf0b0d7d6a40fb30ab7, < 5224bd37e37d36076a550d99b2aebba33939fd95
  • >= f889491380582b4ba2981cf0b0d7d6a40fb30ab7, < 54617e9119be2eb728ecdd8d977b99c99d4c498a
  • >= f889491380582b4ba2981cf0b0d7d6a40fb30ab7, < 13fa6f32a56a386a82bd7451644c494beed034af
  • >= f889491380582b4ba2981cf0b0d7d6a40fb30ab7, < cf363a7a02ce132ef1f58084fdb13e1a3b7da7e7
  • >= f889491380582b4ba2981cf0b0d7d6a40fb30ab7, < 6fa3e9b1fe856259555a7e22f3f3082e7827fd9b
  • >= f889491380582b4ba2981cf0b0d7d6a40fb30ab7, < f1e21108e3ddfcce62f6cad4ebd7b5674543c9e6
  • >= f889491380582b4ba2981cf0b0d7d6a40fb30ab7, < b70ebe0bba254e093dd5fd4c0c170941ce83eb85
  • >= f889491380582b4ba2981cf0b0d7d6a40fb30ab7, < de845981da67a6b049080c87e605130b0c30adc5

Fixed in 5224bd37e37d36076a550d99b2aebba33939fd95, 54617e9119be2eb728ecdd8d977b99c99d4c498a, 13fa6f32a56a386a82bd7451644c494beed034af, cf363a7a02ce132ef1f58084fdb13e1a3b7da7e7, 6fa3e9b1fe856259555a7e22f3f3082e7827fd9b, f1e21108e3ddfcce62f6cad4ebd7b5674543c9e6, b70ebe0bba254e093dd5fd4c0c170941ce83eb85, de845981da67a6b049080c87e605130b0c30adc5

Linux Linux
  • 4.11

Fixed in 0, 5.10.265, 5.15.216, 6.1.183, 6.6.152, 6.12.104, 6.18.45, 7.1.9, 7.2

Mitigation

Upgrade Linux to 5224bd37e37d36076a550d99b2aebba33939fd95 or 54617e9119be2eb728ecdd8d977b99c99d4c498a or 13fa6f32a56a386a82bd7451644c494beed034af or cf363a7a02ce132ef1f58084fdb13e1a3b7da7e7 or 6fa3e9b1fe856259555a7e22f3f3082e7827fd9b or f1e21108e3ddfcce62f6cad4ebd7b5674543c9e6 or b70ebe0bba254e093dd5fd4c0c170941ce83eb85 or de845981da67a6b049080c87e605130b0c30adc5 or later.

Upgrade Linux to 0 or 5.10.265 or 5.15.216 or 6.1.183 or 6.6.152 or 6.12.104 or 6.18.45 or 7.1.9 or 7.2 or later.

Timeline

Days relative to CVE publication
t=0+7+14+21+28+35+42+49CVE published21 Aug 2026 · t = 0First public PoC14 Oct 2026 · t+54d

First public PoC 54 days after publication; not in CISA KEV. First PoC: ABC00012345/CVE-2026-74580 (created 14 Oct 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

2 PoCs · 1 pending · 1 informational

PoCs 2
RepositoryCreatedFound by usStarsAssessment
ABC00012345/CVE-2026-74580 14 Oct 2026 +54 d backfilled 2 PoC
YounesHfa/CVE-2026-74580 25 Oct 2026 +65 d 14 Nov 2026 3 PoC
Pending 1
RepositoryCreatedFound by usStarsAssessment
V01DL1NG/vghost-watch 17 Oct 2026 +57 d 14 Nov 2026 1 Pending
Informational 1
RepositoryCreatedStarsAssessment
techupdate24/linux-kernel-cve-2026-74580-vghost 14 Oct 2026 +54 d 0 Informational · write-up

Only PoCs count toward the first-PoC date and the characteristics below. "Backfilled" means we found the repository more than 30 days after it was created. Do not run PoC code from unknown sources.