Back to CVE records
High 8.8Published Aug 21, 2026

CVE-2026-74580vhost: reset the vring metadata cache on vring reconfiguration

Updated under an hour ago ()

Does this affect you?

It affects Linux. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
8.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Weakness (CWE)
Not given
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Linux
NVD analysis
Received
Record last updated
Oct 16, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
from f889491380582b4ba2981cf0b0d7d6a40fb30ab7 before 5224bd37e37d36076a550d99b2aebba33939fd95; from f889491380582b4ba2981cf0b0d7d6a40fb30ab7 before 54617e9119be2eb728ecdd8d977b99c99d4c498a; from f889491380582b4ba2981cf0b0d7d6a40fb30ab7 before 13fa6f32a56a386a82bd7451644c494beed034af; from f889491380582b4ba2981cf0b0d7d6a40fb30ab7 before cf363a7a02ce132ef1f58084fdb13e1a3b7da7e7; from f889491380582b4ba2981cf0b0d7d6a40fb30ab7 before 6fa3e9b1fe856259555a7e22f3f3082e7827fd9b; from f889491380582b4ba2981cf0b0d7d6a40fb30ab7 before f1e21108e3ddfcce62f6cad4ebd7b5674543c9e6; from f889491380582b4ba2981cf0b0d7d6a40fb30ab7 before b70ebe0bba254e093dd5fd4c0c170941ce83eb85; from f889491380582b4ba2981cf0b0d7d6a40fb30ab7 before de845981da67a6b049080c87e605130b0c30adc5
CNA record

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.