https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 18:56:48 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-07749 bdu:2024-07749 https://cve.radiocsirt.org/vuln/bdu:2024-07749 https://cve.radiocsirt.org/vuln/bell-cve-2024-42072 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2024-42072 https://cve.radiocsirt.org/vuln/euvd-2026-345953 EUVD-2026-345953 https://cve.radiocsirt.org/vuln/euvd-2026-345953 https://cve.radiocsirt.org/vuln/fkie_cve-2024-42072 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>bpf: Fix may_goto with negative offset.</p> <p>Zac&#39;s syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto is patched. When offset is negative it should be patched differently. The 2nd bug is in the verifier: when current state may_goto_depth is equal to visited state may_goto_depth it means there is an actual infinite loop. It&#39;s not correct to prune exploration of the program at this point. Note, that this check doesn&#39;t limit the program to only one may_goto insn, since 2nd and any further may_goto will increment may_goto_depth only in the queued state pushed for future exploration. The current state will have may_goto_depth == 0 regardless of number of may_goto insns and the verifier has to explore the program until bpf_exit.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>bpf: Fix may_goto with negative offset.</p> <p>Zac&#39;s syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto is patched. When offset is negative it should be patched differently. The 2nd bug is in the verifier: when current state may_goto_depth is equal to visited state may_goto_depth it means there is an actual infinite loop. It&#39;s not correct to prune exploration of the program at this point. Note, that this check doesn&#39;t limit the program to only one may_goto insn, since 2nd and any further may_goto will increment may_goto_depth only in the queued state pushed for future exploration. The current state will have may_goto_depth == 0 regardless of number of may_goto insns and the verifier has to explore the program until bpf_exit.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-42072 https://cve.radiocsirt.org/vuln/ghsa-hwc3-9p27-c4j6 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>bpf: Fix may_goto with negative offset.</p> <p>Zac&#39;s syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto is patched. When offset is negative it should be patched differently. The 2nd bug is in the verifier: when current state may_goto_depth is equal to visited state may_goto_depth it means there is an actual infinite loop. It&#39;s not correct to prune exploration of the program at this point. Note, that this check doesn&#39;t limit the program to only one may_goto insn, since 2nd and any further may_goto will increment may_goto_depth only in the queued state pushed for future exploration. The current state will have may_goto_depth == 0 regardless of number of may_goto insns and the verifier has to explore the program until bpf_exit.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>bpf: Fix may_goto with negative offset.</p> <p>Zac&#39;s syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto is patched. When offset is negative it should be patched differently. The 2nd bug is in the verifier: when current state may_goto_depth is equal to visited state may_goto_depth it means there is an actual infinite loop. It&#39;s not correct to prune exploration of the program at this point. Note, that this check doesn&#39;t limit the program to only one may_goto insn, since 2nd and any further may_goto will increment may_goto_depth only in the queued state pushed for future exploration. The current state will have may_goto_depth == 0 regardless of number of may_goto insns and the verifier has to explore the program until bpf_exit.</p> https://cve.radiocsirt.org/vuln/ghsa-hwc3-9p27-c4j6 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-42072 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 66 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: bpf: Fix may_goto with negative offset. Zac&#39;s syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto is patched. When offset is negative it should be patched differently. The 2nd bug is in the verifier: when current state may_goto_depth is equal to visited state may_goto_depth it means there is an actual infinite loop. It&#39;s not correct to prune exploration of the program at this point. Note, that this check doesn&#39;t limit the program to only one may_goto insn, since 2nd and any further may_goto will increment may_goto_depth only in the queued state pushed for future exploration. The current state will have may_goto_depth == 0 regardless of number of may_goto insns and the verifier has to explore the program until bpf_exit.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 66 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: bpf: Fix may_goto with negative offset. Zac&#39;s syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto is patched. When offset is negative it should be patched differently. The 2nd bug is in the verifier: when current state may_goto_depth is equal to visited state may_goto_depth it means there is an actual infinite loop. It&#39;s not correct to prune exploration of the program at this point. Note, that this check doesn&#39;t limit the program to only one may_goto insn, since 2nd and any further may_goto will increment may_goto_depth only in the queued state pushed for future exploration. The current state will have may_goto_depth == 0 regardless of number of may_goto insns and the verifier has to explore the program until bpf_exit.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-42072 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1722 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1722