vhost-scsi: flush backend after device ioctls
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 057cbf49a1f08297877e46c82f707b1bfea806a8 · < 6c1b802e36b05ebd9d41686c4dce6f06966af469| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
In the Linux kernel’s vhost-scsi backend, an in-flight command can retain response buffers mapped through an old memory table after VHOST_SET_MEM_TABLE replaces it. If that mapping is reused, command completion can write a response to an unrelated userspace object. This requires a device ioctl while a command is in flight; the input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with vhost-scsi should check whether their kernel includes the fix; affected versions are not specified.