<?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>Mon, 28 Sep 2026 06:37:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53221 — ip6_vti: fix incorrect tunnel matching in vti6_tnl_lookup()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-53221</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;ip6_vti: fix incorrect tunnel matching in vti6_tnl_lookup()&lt;/p&gt;
&lt;p&gt;In vti6_tnl_lookup(), when an exact match for a tunnel fails,
the code falls back to searching for wildcard tunnels:&lt;/p&gt;
&lt;p&gt;- Tunnels matching the packet&amp;#39;s local address, with any remote address
  wildcard remote).&lt;/p&gt;
&lt;p&gt;- Tunnels matching the packet&amp;#39;s remote address, with any local address
  (wildcard local).&lt;/p&gt;
&lt;p&gt;However, vti6 stores all these different types of tunnels in the same
hash table (ip6n-&amp;gt;tnls_r_l) prone to hash collisions.&lt;/p&gt;
&lt;p&gt;The bug is that the fallback search loops in vti6_tnl_lookup() were
missing checks to ensure that the candidate tunnel actually has
a wildcard address.&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;ip6_vti: fix incorrect tunnel matching in vti6_tnl_lookup()&lt;/p&gt;
&lt;p&gt;In vti6_tnl_lookup(), when an exact match for a tunnel fails,
the code falls back to searching for wildcard tunnels:&lt;/p&gt;
&lt;p&gt;- Tunnels matching the packet&amp;#39;s local address, with any remote address
  wildcard remote).&lt;/p&gt;
&lt;p&gt;- Tunnels matching the packet&amp;#39;s remote address, with any local address
  (wildcard local).&lt;/p&gt;
&lt;p&gt;However, vti6 stores all these different types of tunnels in the same
hash table (ip6n-&amp;gt;tnls_r_l) prone to hash collisions.&lt;/p&gt;
&lt;p&gt;The bug is that the fallback search loops in vti6_tnl_lookup() were
missing checks to ensure that the candidate tunnel actually has
a wildcard address.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-53221</guid>
    </item>
  </channel>
</rss>
