{"vulnerability": "CVE-2024-44996", "sightings": [{"uuid": "3c39e53f-a66b-4bca-bf2c-93daa0240bba", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-44996", "type": "seen", "source": "https://t.me/cvedetector/4866", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-44996 - Linux Kernel vsock BPF Recursion Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-44996 \nPublished : Sept. 4, 2024, 8:15 p.m. | 27\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nvsock: fix recursive ->recvmsg calls  \n  \nAfter a vsock socket has been added to a BPF sockmap, its prot->recvmsg  \nhas been replaced with vsock_bpf_recvmsg(). Thus the following  \nrecursiion could happen:  \n  \nvsock_bpf_recvmsg()  \n -> __vsock_recvmsg()  \n  -> vsock_connectible_recvmsg()  \n   -> prot->recvmsg()  \n    -> vsock_bpf_recvmsg() again  \n  \nWe need to fix it by calling the original ->recvmsg() without any BPF  \nsockmap logic in __vsock_recvmsg(). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"04 Sep 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-09-04T22:47:37.000000Z"}]}