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.
Published: 2026-08-21
Score: 8.8 High
EPSS: < 1% Very Low
KEV: No
Impact: Privilege Escalation via out‑of‑bounds memory access in the Linux kernel vhost VRing subsystem
Action: Patch kernel
AI Analysis

Impact

The Linux kernel’s vhost virtualization framework contains a flaw that fails to reset the vring metadata cache when a device IOTLB is reconfigured. This omission leads to a buffer validation (CWE‑825) weakness, allowing a local attacker to trigger out‑of‑bounds memory accesses. By issuing VHOST_SET_VRING_ADDR or VHOST_SET_VRING_NUM ioctl calls while a device IOTLB is attached, the attacker can manipulate the stale cache, causing the kernel to translate a guest virtual address through an invalid mapping, corrupt kernel memory and potentially execute arbitrary code.

Affected Systems

All Linux kernel builds that include the vhost module and use device IOTLBs are potentially affected. The vulnerability is not tied to a specific release number; any recent kernel containing the unpatched vhost code that performs VRing reconfiguration while a device IOTLB is attached is vulnerable.

Risk and Exploitability

The likely attack vector is the local ioctl interface to vhost devices, requiring the attacker to have the ability to send ioctl requests to the device. No publicly available exploits have been reported. The EPSS score is < 1%, indicating a very low probability of exploitation; the CVSS score of 8.8 indicates high severity. The risk is moderate to high for systems that can interact with vhost devices and perform VRing reconfigurations. The vulnerability is not listed in the CISA KEV catalog.

Generated by OpenCVE AI on August 25, 2026 at 06:28 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the patch resetting the vring metadata cache on VRing reconfiguration.
  • If a kernel update is not immediately possible, stop the vhost device before invoking VHOST_SET_VRING_ADDR or VHOST_SET_VRING_NUM, reinitialize the device, and then perform the VRing reconfiguration to force the cache reset.
  • Disable the vhost module or avoid using device IOTLBs on affected kernels until the patch is applied.

Generated by OpenCVE AI on August 25, 2026 at 06:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4777-1 linux security update
Debian DSA Debian DSA DSA-6466-1 linux security update
History

Tue, 25 Aug 2026 05:45:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H'}


Sat, 22 Aug 2026 02:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416
CWE-665

Sat, 22 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-825
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Moderate


Fri, 21 Aug 2026 18:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416
CWE-665

Fri, 21 Aug 2026 16:45:00 +0000

Type Values Removed Values Added
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.
Title vhost: reset the vring metadata cache on vring reconfiguration
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-25T05:40:06.380Z

Reserved: 2026-08-15T05:44:03.918Z

Link: CVE-2026-74580

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-21T17:16:44.210

Modified: 2026-08-25T06:18:30.997

Link: CVE-2026-74580

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-21T00:00:00Z

Links: CVE-2026-74580 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-25T06:30:04Z

Weaknesses
  • CWE-825

    Expired Pointer Dereference