vsock: Update rx_bytes on read_skb()
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 |
|
|
6.6.596.11.66.12In the Linux kernel, the following vulnerability has been resolved:
vsock: Update rx_bytes on read_skb()
Make sure virtio_transport_inc_rx_pkt() and virtio_transport_dec_rx_pkt() calls are balanced (i.e. virtio_vsock_sock::rx_bytes doesn't lie) after vsock_transport::read_skb().
While here, also inform the peer that we've freed up space and it has more credit.
Failing to update rx_bytes after packet is dequeued leads to a warning on SOCK_STREAM recv():
[ 233.396654] rx_queue is empty, but rx_bytes is non-zero [ 233.396702] WARNING: CPU: 11 PID: 40601 at net/vmw_vsock/virtio_transport_common.c:589
From the CVE record · Linux
The Linux kernel's vsock transport can leave its received-byte count incorrect after read_skb() dequeues a packet. A subsequent SOCK_STREAM receive can trigger a kernel warning; the input does not specify an attacker path, authentication requirements, or user interaction.
Engineers running Linux kernels that use vsock should check whether their kernel is affected; affected versions are not specified.