{"vulnerability": "CVE-2024-50169", "sightings": [{"uuid": "a33cf527-2b69-4c38-9c7f-9e0585ecf700", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50169", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113441409630594716", "content": "", "creation_timestamp": "2024-11-07T11:22:20.852309Z"}, {"uuid": "85bc3c70-c2ca-4050-aeb1-eb5350dbe966", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50169", "type": "seen", "source": "https://t.me/cvedetector/10062", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50169 - Virtio Transport Vsock Rx Bytes Inconsistency Vulnerability in Linux Kernel\", \n  \"Content\": \"CVE ID : CVE-2024-50169 \nPublished : Nov. 7, 2024, 10:15 a.m. | 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nvsock: Update rx_bytes on read_skb()  \n  \nMake sure virtio_transport_inc_rx_pkt() and virtio_transport_dec_rx_pkt()  \ncalls are balanced (i.e. virtio_vsock_sock::rx_bytes doesn't lie) after  \nvsock_transport::read_skb().  \n  \nWhile here, also inform the peer that we've freed up space and it has more  \ncredit.  \n  \nFailing to update rx_bytes after packet is dequeued leads to a warning on  \nSOCK_STREAM recv():  \n  \n[  233.396654] rx_queue is empty, but rx_bytes is non-zero  \n[  233.396702] WARNING: CPU: 11 PID: 40601 at net/vmw_vsock/virtio_transport_common.c:589 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"07 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-07T11:54:16.000000Z"}]}