{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97988 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97988 is a vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-97988 and fix it if it is affected.\n\nWhat it is: CVE-2026-97988 is a vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-97988 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-97988/ (Markdown: https://insights.sbomify.com/CVE-2026-97988/index.md)","id":"CVE-2026-97988","markdown":"https://insights.sbomify.com/CVE-2026-97988/index.md","name":"CVE-2026-97988","record":{"aliases":["AZL-104721","BELL-CVE-2026-97988","DEBIAN-CVE-2026-97988","GHSA-xcf7-28q5-2jrx","UBUNTU-CVE-2026-97988"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel vhost","requires_auth":"high_privilege","summary":"A race condition in the Linux kernel vhost driver allows stale ring mappings during IOTLB transitions, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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 address space. Keeping them\nacross the transition can leave stale ring mappings in use.\n\nClearing d-\u003eiotlb before taking the VQ locks also lets a worker observe\na transient NULL d-\u003eiotlb and fall back to d-\u003eumem 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"vhost: invalidate vring access on IOTLB transitions","id":"CVE-2026-97988","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"vduse: validate virtqueue alignment","id":"CVE-2026-97989"},"packages":[],"prev":{"headline":"virtio_input: reset device if input_register_device() fails","id":"CVE-2026-97987"},"products":["Linux"],"published":"2026-09-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A race condition in the Linux kernel vhost driver allows stale ring mappings during IOTLB transitions, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-97988/"}