vhost-scsi: protect vq->log_used with vq->mutex
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 057cbf49a1f08297877e46c82f707b1bfea806a8 · < c0039e3afda29be469d29b3013d7f9bdee136834| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
A race in the Linux kernel's vhost-scsi completion and control queue paths can access a logging buffer after QEMU frees it. This can cause invalid writes to QEMU user-space memory when QEMU disables used-ring logging while either path is active. The input does not specify an attacker access or authentication requirement.
Engineers running Linux systems that use vhost-scsi with QEMU should check their kernel versions; affected versions are not specified.