Linux vulnerability

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.

Published 24 Sep 2026Updated 25 Sep 20263 sources
CVSS 7.8

What happened

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.

Affected versions

Linux: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before 981c97d09c6b9560bb12dcc41f11ce59b1a48e97 (git); 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before 6c1b802e36b05ebd9d41686c4dce6f06966af469 (git); 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 through before 22598f55a4c2b510b3df5e69e563387a963222ae (git); before 6.12.111 (semver); before 6.18.53 (semver) Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.