We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
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
Reserved 2024-10-21 | Published 2024-11-07 | Updated 2024-11-19 | Assigner Linuxgit.kernel.org/...c/66cd51de31c682a311c2fa25c580b7ea45859dd9
git.kernel.org/...c/e5ca2b98090b4bb1c393088c724af6c37812a829
git.kernel.org/...c/3543152f2d330141d9394d28855cb90b860091d2
Support options