{"id":"CVE-2026-97988","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nvhost: invalidate vring access on IOTLB transitions\n\nWhen VIRTIO_F_ACCESS_PLATFORM changes, cached vring pointers and IOTLB\nmetadata are interpreted in a different addr…","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nvhost: invalidate vring access on IOTLB transitions\n\nWhen VIRTIO_F_ACCESS_PLATFORM changes, cached vring pointers and IOTLB\nmetadata are interpreted in a different addr…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c < 4a454af8e56c1596ada1421ae5eba90c8896c7c7","Linux >= 6b1e6cc7855b09a0a9bfa1d9f30172ba366f161c < e4f4761879a230aa59e569102a6ab9851847d833","Linux 4.8"],"published":"2026-09-25","updated":"2026-09-25","sourceUpdated":"2026-09-25T11:17:26.903","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-97988","references":[{"url":"https://git.kernel.org/stable/c/4a454af8e56c1596ada1421ae5eba90c8896c7c7","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/e4f4761879a230aa59e569102a6ab9851847d833","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"ingestedAt":"2026-09-25T11:06:38.866Z","slug":"CVE-2026-97988","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvhost: invalidate vring access on IOTLB transitions\n\nWhen VIRTIO_F_ACCESS_PLATFORM changes, cached vring pointers and IOTLB\nmetadata are interpreted in a different address space. Keeping them\nacross the transition can leave stale ring mappings in use.\n\nClearing d->iotlb before taking the VQ locks also lets a worker observe\na transient NULL d->iotlb and fall back to d->umem while translating a\ndescriptor.\n\nAdd a common vhost_clear_device_iotlb() helper for vhost-net and\nvhost-vsock. Take all VQ mutexes in index order before dropping the\ndevice-wide IOTLB, invalidate each VQ's cached ring access and metadata,\nclear pending IOTLB messages, and free the old table after the handoff.\nThis serializes the transition with workers and prevents mixed address\nspace mappings.\n\nOn the first direct-to-IOTLB transition, invalidate the cached vring\naddresses. When an existing device IOTLB is replaced, preserve the\nGIOVA ring addresses and reset only the metadata cache. After clearing\nACCESS_PLATFORM, userspace must configure the vring addresses for the\nnew address mode.\n\nvhost_vq_invalidate_access() clears desc, avail, and used together.\nTreat the VQ as invalidated only when all three are NULL, since a single\nGIOVA address may legitimately be zero.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}