vsock: Update rx_bytes on read_skb()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3543152f2d330141d9394d28855cb90b860091d2, Kernel 66cd51de31c682a311c2fa25c580b7ea45859dd9 and Kernel e5ca2b98090b4bb1c393088c724af6c37812a829.
In 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
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.4, >=634f1a7110b439c65fd8a809171c1d2d28bcea6f <3543152f2d330141d9394d28855cb90b860091d2, >=634f1a7110b439c65fd8a809171c1d2d28bcea6f <66cd51de31c682a311c2fa25c580b7ea45859dd9, >=634f1a7110b439c65fd8a809171c1d2d28bcea6f <e5ca2b98090b4bb1c393088c724af6c37812a829 | 3543152f2d330141d9394d28855cb90b860091d2, 66cd51de31c682a311c2fa25c580b7ea45859dd9, e5ca2b98090b4bb1c393088c724af6c37812a829 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket