<?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>Sun, 04 Oct 2026 15:32:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43453 — netfilter: nft_set_pipapo: fix stack out-of-bounds read in pipapo_drop()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43453</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;netfilter: nft_set_pipapo: fix stack out-of-bounds read in pipapo_drop()&lt;/p&gt;
&lt;p&gt;pipapo_drop() passes rulemap[i + 1].n to pipapo_unmap() as the
to_offset argument on every iteration, including the last one where
i == m-&amp;gt;field_count - 1. This reads one element past the end of the
stack-allocated rulemap array (declared as rulemap[NFT_PIPAPO_MAX_FIELDS]
with NFT_PIPAPO_MAX_FIELDS == 16).&lt;/p&gt;
&lt;p&gt;Although pipapo_unmap() returns early when is_last is true without
using the to_offset value, the argument is evaluated at the call site
before the function body executes, making this a genuine out-of-bounds
stack read confirmed by KASAN:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: stack-out-of-bounds in pipapo_drop+0x50c/0x57c [nf_tables]
  Read of size 4 at addr ffff8000810e71a4&lt;/p&gt;
&lt;p&gt;This frame has 1 object:
   [32, 160) &amp;#39;rulemap&amp;#39;&lt;/p&gt;
&lt;p&gt;The buggy address is at offset 164 -- exactly 4 bytes past the end
  of the rulemap array.&lt;/p&gt;
&lt;p&gt;Pass 0 instead of rulemap[i + 1].n on the last iteration to avoid
the out-of-bounds read.&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;netfilter: nft_set_pipapo: fix stack out-of-bounds read in pipapo_drop()&lt;/p&gt;
&lt;p&gt;pipapo_drop() passes rulemap[i + 1].n to pipapo_unmap() as the
to_offset argument on every iteration, including the last one where
i == m-&amp;gt;field_count - 1. This reads one element past the end of the
stack-allocated rulemap array (declared as rulemap[NFT_PIPAPO_MAX_FIELDS]
with NFT_PIPAPO_MAX_FIELDS == 16).&lt;/p&gt;
&lt;p&gt;Although pipapo_unmap() returns early when is_last is true without
using the to_offset value, the argument is evaluated at the call site
before the function body executes, making this a genuine out-of-bounds
stack read confirmed by KASAN:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: stack-out-of-bounds in pipapo_drop+0x50c/0x57c [nf_tables]
  Read of size 4 at addr ffff8000810e71a4&lt;/p&gt;
&lt;p&gt;This frame has 1 object:
   [32, 160) &amp;#39;rulemap&amp;#39;&lt;/p&gt;
&lt;p&gt;The buggy address is at offset 164 -- exactly 4 bytes past the end
  of the rulemap array.&lt;/p&gt;
&lt;p&gt;Pass 0 instead of rulemap[i + 1].n on the last iteration to avoid
the out-of-bounds read.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43453</guid>
    </item>
  </channel>
</rss>
