CVE-2026-97988

vhost: invalidate vring access on IOTLB transitions

Description

In the Linux kernel, the following vulnerability has been resolved: vhost: invalidate vring access on IOTLB transitions When VIRTIO_F_ACCESS_PLATFORM changes, cached vring pointers and IOTLB metadata are interpreted in a different address space. Keeping them across the transition can leave stale ring mappings in use. Clearing d->iotlb before taking the VQ locks also lets a worker observe a transient NULL d->iotlb and fall back to d->umem while translating a descriptor. Add a common vhost_clear_device_iotlb() helper for vhost-net and vhost-vsock. Take all VQ mutexes in index order before dropping the device-wide IOTLB, invalidate each VQ's cached ring access and metadata, clear pending IOTLB messages, and free the old table after the handoff. This serializes the transition with workers and prevents mixed address space mappings. On the first direct-to-IOTLB transition, invalidate the cached vring addresses. When an existing device IOTLB is replaced, preserve the GIOVA ring addresses and reset only the metadata cache. After clearing ACCESS_PLATFORM, userspace must configure the vring addresses for the new address mode. vhost_vq_invalidate_access() clears desc, avail, and used together. Treat the VQ as invalidated only when all three are NULL, since a single GIOVA address may legitimately be zero.

Key facts

Published
25 Sep 2026
Last changed
21 Oct 2026
Assigned by
Linux
EPSS
0.168% likely to be exploited in the next 30 days, higher than 6.206% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c up to but excluding 021bf73731f7aa94540a549cf850db5968019960 (affected)
  • 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c up to but excluding e8fe13c14d57cc7c6bd69c72c5fabaaf0d918f98 (affected)
  • 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c up to but excluding 7f8ee0b8f632441aec456a7c147fb43f5c73542d (affected)
  • 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c up to but excluding 4a454af8e56c1596ada1421ae5eba90c8896c7c7 (affected)
  • 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c up to but excluding e4f4761879a230aa59e569102a6ab9851847d833 (affected)
LinuxLinux
  • Default status: affected
  • 4.8 (affected)
  • 0 up to but excluding 4.8 (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.114 up to and including 6.12.* (unaffected)
  • 6.18.57 up to and including 6.18.* (unaffected)
  • 7.2.7 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 25 Sep 2026 Published

References