{"uuid": "a9dabcc8-2f56-485a-b884-2670f02b3e0e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-42072", "type": "seen", "source": "https://t.me/cvedetector/1883", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42072 - Linux Kernel BPF May-Goto Offsets Infinite Loop Denial of Service\", \n  \"Content\": \"CVE ID : CVE-2024-42072 \nPublished : July 29, 2024, 4:15 p.m. | 26\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf: Fix may_goto with negative offset.  \n  \nZac's syzbot crafted a bpf prog that exposed two bugs in may_goto.  \nThe 1st bug is the way may_goto is patched. When offset is negative  \nit should be patched differently.  \nThe 2nd bug is in the verifier:  \nwhen current state may_goto_depth is equal to visited state may_goto_depth  \nit means there is an actual infinite loop. It's not correct to prune  \nexploration of the program at this point.  \nNote, that this check doesn't limit the program to only one may_goto insn,  \nsince 2nd and any further may_goto will increment may_goto_depth only  \nin the queued state pushed for future exploration. The current state  \nwill have may_goto_depth == 0 regardless of number of may_goto insns  \nand the verifier has to explore the program until bpf_exit. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T18:48:39.000000Z"}