<?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-09-29T11:29:28.584987+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-2026-53221</id>
    <title>CVE-2026-53221 — ip6_vti: fix incorrect tunnel matching in vti6_tnl_lookup()</title>
    <updated>2026-09-29T11:29:28.607074+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>ip6_vti: fix incorrect tunnel matching in vti6_tnl_lookup()</p>
<p>In vti6_tnl_lookup(), when an exact match for a tunnel fails,
the code falls back to searching for wildcard tunnels:</p>
<p>- Tunnels matching the packet's local address, with any remote address
  wildcard remote).</p>
<p>- Tunnels matching the packet's remote address, with any local address
  (wildcard local).</p>
<p>However, vti6 stores all these different types of tunnels in the same
hash table (ip6n-&gt;tnls_r_l) prone to hash collisions.</p>
<p>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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-53221"/>
  </entry>
</feed>
