In the Linux kernel, the following vulnerability has been resolved:
vhost-scsi: protect vq->log_used with vq->mutex
The vhost-scsi completion path may access vq->log_base when vq->log_used is already set to false.
vhost-thread QEMU-thread
vhost_scsi_complete_cmd_work() -> vhost_add_used() -> vhost_add_used_n() if (unlikely(vq->log_used)) QEMU disables vq->log_used via VHOST_SET_VRING_ADDR. mutex_lock(&vq->mutex); vq->log_used = false now! mutex_unlock(&vq->mutex);
QEMU gfree(vq->log_base)
log_used()
-> log_write(vq->log_base)
Assuming the VMM is QEMU. The vq->log_base is from QEMU userpace and can be reclaimed via gfree(). As a result, this causes invalid memory writes to QEMU userspace.
The control queue path has the same issue.
| Software | From | Fixed in |
|---|---|---|
| linux / linux_kernel | - | 5.10.240 |
| linux / linux_kernel | 5.11 | 5.15.189 |
| linux / linux_kernel | 5.16 | 6.1.146 |
| linux / linux_kernel | 6.2 | 6.6.93 |
| linux / linux_kernel | 6.7 | 6.12.31 |
| linux / linux_kernel | 6.13 | 6.14.9 |
| linux / linux_kernel | 6.15-rc1 | 6.15-rc1.x |
| linux / linux_kernel | 6.15-rc2 | 6.15-rc2.x |
| linux / linux_kernel | 6.15-rc3 | 6.15-rc3.x |
| debian / debian_linux | 11.0 | 11.0.x |