<?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>Thu, 01 Oct 2026 01:50:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80634 — netfilter: flowtable: avoid num_encaps underflow on bridge VLAN untag</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80634</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: flowtable: avoid num_encaps underflow on bridge VLAN untag&lt;/p&gt;
&lt;p&gt;The DEV_PATH_BR_VLAN_UNTAG case post-decrements info-&amp;gt;num_encaps
inside WARN_ON_ONCE(). num_encaps is u8, so if it&amp;#39;s already 0 the
decrement still happens and wraps it to 255. The break only leaves
the inner switch -- a later path entry can set info-&amp;gt;indev back to
a real device, and we end up returning with num_encaps == 255.&lt;/p&gt;
&lt;p&gt;nft_dev_forward_path() then walks info.encap[] (size 2) up to
num_encaps, which means an OOB stack read and a bogus count copied
into the route descriptor.&lt;/p&gt;
&lt;p&gt;Should only happen on a malformed bridge path stack, hence the WARN,
but worth handling sanely. Move the decrement out of the WARN.&lt;/p&gt;
&lt;p&gt;[ While at this, remove the WARN_ON_ONCE since this can only happen
  with a buggy bridge path stack --pablo ].&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: flowtable: avoid num_encaps underflow on bridge VLAN untag&lt;/p&gt;
&lt;p&gt;The DEV_PATH_BR_VLAN_UNTAG case post-decrements info-&amp;gt;num_encaps
inside WARN_ON_ONCE(). num_encaps is u8, so if it&amp;#39;s already 0 the
decrement still happens and wraps it to 255. The break only leaves
the inner switch -- a later path entry can set info-&amp;gt;indev back to
a real device, and we end up returning with num_encaps == 255.&lt;/p&gt;
&lt;p&gt;nft_dev_forward_path() then walks info.encap[] (size 2) up to
num_encaps, which means an OOB stack read and a bogus count copied
into the route descriptor.&lt;/p&gt;
&lt;p&gt;Should only happen on a malformed bridge path stack, hence the WARN,
but worth handling sanely. Move the decrement out of the WARN.&lt;/p&gt;
&lt;p&gt;[ While at this, remove the WARN_ON_ONCE since this can only happen
  with a buggy bridge path stack --pablo ].&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80634</guid>
    </item>
  </channel>
</rss>
