vhost: invalidate vring access on IOTLB transitions
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.114, 6.18.57, 7.2.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c · fixed in 021bf73731f7aa94540a549cf850db5968019960; From 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c · fixed in e8fe13c14d57cc7c6bd69c72c5fabaaf0d918f98; From 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c · fixed in 7f8ee0b8f632441aec456a7c147fb43f5c73542d; From 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c · fixed in 4a454af8e56c1596ada1421ae5eba90c8896c7c7; From 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c · fixed in e4f4761879a230aa59e569102a6ab9851847d833
- Linux Linux
4.8
- KernelLinux
From 4.8.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.7