{"vulnerability": "CVE-2024-43873", "sightings": [{"uuid": "45726f6e-4b9b-49ac-a650-9694c4ab8348", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-43873", "type": "seen", "source": "https://t.me/cvedetector/3715", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-43873 - Linux Kernel Vhost vsock Sequence Packet Allow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-43873 \nPublished : Aug. 21, 2024, 1:15 a.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nvhost/vsock: always initialize seqpacket_allow  \n  \nThere are two issues around seqpacket_allow:  \n1. seqpacket_allow is not initialized when socket is  \n   created. Thus if features are never set, it will be  \n   read uninitialized.  \n2. if VIRTIO_VSOCK_F_SEQPACKET is set and then cleared,  \n   then seqpacket_allow will not be cleared appropriately  \n   (existing apps I know about don't usually do this but  \n    it's legal and there's no way to be sure no one relies  \n    on this).  \n  \nTo fix:  \n - initialize seqpacket_allow after allocation  \n - set it unconditionally in set_features \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-21T04:00:41.000000Z"}]}