vsock/virtio: fix potential unbounded skb queue
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
vsock/virtio: fix potential unbounded skb queue
virtio_transport_inc_rx_pkt() checks vvs->rx_bytes + len > vvs->buf_alloc.
virtio_transport_recv_enqueue() skips coalescing for packets with VIRTIO_VSOCK_SEQ_EOM.
If fed with packets with len == 0 and VIRTIO_VSOCK_SEQ_EOM, a very large number of packets can be queued because vvs->rx_bytes stays at 0.
Fix this by estimating the skb metadata size:
(Number of skbs in the queue) * SKB_TRUESIZE(0)
From the CVE record · Linux
The Linux kernel’s vsock/virtio receive path can queue an unbounded number of packets when fed zero-length packets marked VIRTIO_VSOCK_SEQ_EOM. This can consume resources because the receive-byte count stays at zero. The input does not specify whether exploitation requires network or local access, authentication, or user interaction.
Engineers running Linux kernels with vsock/virtio should check their versions against the vendor advisory; affected versions are not specified.