<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 22:38:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40169 — bpf: Reject negative offsets for ALU ops</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40169</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Reject negative offsets for ALU ops&lt;/p&gt;
&lt;p&gt;When verifying BPF programs, the check_alu_op() function validates
instructions with ALU operations. The &amp;#39;offset&amp;#39; field in these
instructions is a signed 16-bit integer.&lt;/p&gt;
&lt;p&gt;The existing check &amp;#39;insn-&amp;gt;off &amp;gt; 1&amp;#39; was intended to ensure the offset is
either 0, or 1 for BPF_MOD/BPF_DIV. However, because &amp;#39;insn-&amp;gt;off&amp;#39; is
signed, this check incorrectly accepts all negative values (e.g., -1).&lt;/p&gt;
&lt;p&gt;This commit tightens the validation by changing the condition to
&amp;#39;(insn-&amp;gt;off != 0 &amp;amp;&amp;amp; insn-&amp;gt;off != 1)&amp;#39;. This ensures that any value
other than the explicitly permitted 0 and 1 is rejected, hardening the
verifier against malformed BPF programs.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Reject negative offsets for ALU ops&lt;/p&gt;
&lt;p&gt;When verifying BPF programs, the check_alu_op() function validates
instructions with ALU operations. The &amp;#39;offset&amp;#39; field in these
instructions is a signed 16-bit integer.&lt;/p&gt;
&lt;p&gt;The existing check &amp;#39;insn-&amp;gt;off &amp;gt; 1&amp;#39; was intended to ensure the offset is
either 0, or 1 for BPF_MOD/BPF_DIV. However, because &amp;#39;insn-&amp;gt;off&amp;#39; is
signed, this check incorrectly accepts all negative values (e.g., -1).&lt;/p&gt;
&lt;p&gt;This commit tightens the validation by changing the condition to
&amp;#39;(insn-&amp;gt;off != 0 &amp;amp;&amp;amp; insn-&amp;gt;off != 1)&amp;#39;. This ensures that any value
other than the explicitly permitted 0 and 1 is rejected, hardening the
verifier against malformed BPF programs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40169</guid>
    </item>
  </channel>
</rss>
