<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T11:07:22.729437+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-22087</id>
    <title>CVE-2025-22087 — bpf: Fix array bounds error with may_goto</title>
    <updated>2026-10-04T11:07:23.211911+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-22087"/>
  </entry>
</feed>
