{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93782 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93782 is a high-severity vulnerability in Linux, published on 24 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-93782 and fix it if it is affected.\n\nWhat it is: CVE-2026-93782 is a high-severity vulnerability in Linux, published on 24 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-93782 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-93782/ (Markdown: https://insights.sbomify.com/CVE-2026-93782/index.md)","id":"CVE-2026-93782","markdown":"https://insights.sbomify.com/CVE-2026-93782/index.md","name":"CVE-2026-93782","record":{"aliases":["AZL-103694","BELL-CVE-2026-93782","DEBIAN-CVE-2026-93782","GHSA-fqh3-m8p8-gg7r","UBUNTU-CVE-2026-93782"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_modify","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel vhost-scsi","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel vhost-scsi driver allows guest VMs to corrupt host memory by exploiting stale iovec mappings during memory table updates.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nvhost-scsi: flush backend after device ioctls\n\nvhost-scsi translates guest response descriptors into userspace iovecs\nwhen commands are submitted.  Target-core completes those commands\nasynchronously, so VHOST_SET_MEM_TABLE can replace the memory table while\nan in-flight command still retains response iovecs translated through the\nold table.\n\nIf the old mapping is reused after VHOST_SET_MEM_TABLE returns, command\ncompletion can write the response to an unrelated userspace object.\n\nFlush the vhost-scsi backend after vhost_dev_ioctl() handles a device\nioctl.  This waits for in-flight commands that can still use the old\nresponse iovecs before the ioctl returns.","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-scsi: flush backend after device ioctls","id":"CVE-2026-93782","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"Bluetooth: RFCOMM: validate skb length in rfcomm_recv_frame","id":"CVE-2026-93783"},"packages":[],"prev":{"headline":"scsi: core: Do not block on tag allocation in scsi_eh_lock_door()","id":"CVE-2026-93781"},"products":["Linux"],"published":"2026-09-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-03","vendors":["Linux"]},"summary":"A race condition in the Linux kernel vhost-scsi driver allows guest VMs to corrupt host memory by exploiting stale iovec mappings during memory table updates.","url":"https://insights.sbomify.com/CVE-2026-93782/"}