scsi: storvsc: Fix swiotlb bounce buffer leak in confidential VM
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
scsi: storvsc: Fix swiotlb bounce buffer leak in confidential VM
storvsc_queuecommand() maps the scatter/gather list using scsi_dma_map(), which in a confidential VM allocates swiotlb bounce buffers. If the I/O submission fails in storvsc_do_io(), the I/O is typically retried by higher level code, but the bounce buffer memory is never freed. The mostly like cause of I/O submission failure is a full VMBus channel ring buffer, which is not uncommon under high I/O loads. Eventually enough bounce buffer memory leaks that the confidential VM can't do any I/O. The same problem can arise in a non-confidential VM with kernel boot parameter swiotlb=force.
Fix this by doing scsi_dma_unmap() in the case of an I/O submission error, which frees the bounce buffer memory.
From the CVE record · Linux
The Linux kernel’s storvsc driver can leak swiotlb bounce buffers when I/O submission fails in a confidential VM, or in a non-confidential VM booted with swiotlb=force. Under high I/O load, a full VMBus channel ring buffer can trigger repeated failures until the VM can no longer perform I/O. The input does not describe an attacker, authentication requirement, or user interaction.
Engineers running Linux VMs that use storvsc, particularly confidential VMs or VMs booted with swiotlb=force; affected versions are not specified.