https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 11:06:47 +0000 https://vulnerability.circl.lu/vuln/cve-2025-22087 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>bpf: Fix array bounds error with may_goto</p> <p>may_goto uses an additional 8 bytes on the stack, which causes the interpreters[] array to go out of bounds when calculating index by stack_size.</p> <p>1. If a BPF program is rewritten, re-evaluate the stack size. For non-JIT cases, reject loading directly.</p> <p>2. For non-JIT cases, calculating interpreters[idx] may still cause out-of-bounds array access, and just warn about it.</p> <p>3. For jit_requested cases, the execution of bpf_func also needs to be warned. So move the definition of function __bpf_prog_ret0_warn out of the macro definition CONFIG_BPF_JIT_ALWAYS_ON.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>bpf: Fix array bounds error with may_goto</p> <p>may_goto uses an additional 8 bytes on the stack, which causes the interpreters[] array to go out of bounds when calculating index by stack_size.</p> <p>1. If a BPF program is rewritten, re-evaluate the stack size. For non-JIT cases, reject loading directly.</p> <p>2. For non-JIT cases, calculating interpreters[idx] may still cause out-of-bounds array access, and just warn about it.</p> <p>3. For jit_requested cases, the execution of bpf_func also needs to be warned. So move the definition of function __bpf_prog_ret0_warn out of the macro definition CONFIG_BPF_JIT_ALWAYS_ON.</p> https://vulnerability.circl.lu/vuln/cve-2025-22087