First published: Thu Nov 07 2024(Updated: )
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
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | >=6.4<6.6.59 | |
Linux Kernel | >=6.7<6.11.6 | |
Linux Kernel | =6.12-rc1 | |
Linux Kernel | =6.12-rc2 | |
Linux Kernel | =6.12-rc3 | |
debian/linux | 5.10.223-1 5.10.226-1 6.1.123-1 6.1.128-1 6.12.12-1 6.12.15-1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2024-50169 is currently classified as moderate.
CVE-2024-50169 affects various versions of the Linux kernel between 6.4 and 6.6.59, as well as specific release candidates of version 6.12.
To fix CVE-2024-50169, you should update your Linux kernel to a version that includes the patch addressing this vulnerability.
CVE-2024-50169 specifically impacts the handling of virtual socket operations in the Linux kernel, affecting the update of rx_bytes.
As of now, there have been no widespread reports of CVE-2024-50169 being actively exploited in the wild.