vsock/virtio: account only unread bytes in read_skb()

Overview

In the Linux kernel, the following vulnerability has been resolved:

vsock/virtio: account only unread bytes in read_skb()

After a partial stream receive, rx_bytes tracks the unread suffix while buf_used and peer credit still cover the whole packet. virtio_transport_read_skb() dequeues that packet but passes pkt_len for both counters, underflowing rx_bytes.

On a connected CID_LOCAL stream with an SK_SKB verdict, a 40-byte read from a 100-byte packet made SIOCINQ report -40, an empty recv return ELOOP, and poll report the empty socket readable. After verdict detach, receiving 40 bytes wrapped the counter to zero and hid those queued bytes until one more byte arrived. The fixed run kept the counter balanced and exposed all queued data immediately.

This was found during an LLM-assisted manual source audit of VSOCK receive accounting while re-evaluating virtio_transport_read_skb() after CVE-2024-50169.

Subtract only skb->len minus the VSOCK offset from rx_bytes. Retain the full packet length for buf_used and peer credit.

Affected

• Linux >= 7893a41deaf28b53036d4ea7cd9f7d54e8874dfc < e4a0028b0d54b2c45e1dc8c0dd95fe3e9236f55b
• Linux >= 45ca7e9f0730ae36fc610e675b990e9cc9ca0714 < 38bad3930b1185dd6c98db3dd342ddc123c6f3ef
• Linux >= 45ca7e9f0730ae36fc610e675b990e9cc9ca0714 < dd4b2f88ee517f9629d0d3dbfced02ffbc33e2dc
• Linux >= 45ca7e9f0730ae36fc610e675b990e9cc9ca0714 < a463f55c791b96cfd12df8b10ea737d45c80bb18
• Linux 17bada47e9ac3621c28e0ffa89af8279fedea00a
• Linux >= 6.12.34 < 6.12.113
• Linux >= 6.15.3 < 6.16
• Linux 6.16

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.