<?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>Fri, 02 Oct 2026 18:54:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21768 — net: ipv6: fix dst ref loops in rpl, seg6 and ioam6 lwtunnels</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-21768</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;net: ipv6: fix dst ref loops in rpl, seg6 and ioam6 lwtunnels&lt;/p&gt;
&lt;p&gt;Some lwtunnels have a dst cache for post-transformation dst.
If the packet destination did not change we may end up recording
a reference to the lwtunnel in its own cache, and the lwtunnel
state will never be freed.&lt;/p&gt;
&lt;p&gt;Discovered by the ioam6.sh test, kmemleak was recently fixed
to catch per-cpu memory leaks. I&amp;#39;m not sure if rpl and seg6
can actually hit this, but in principle I don&amp;#39;t see why not.&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;net: ipv6: fix dst ref loops in rpl, seg6 and ioam6 lwtunnels&lt;/p&gt;
&lt;p&gt;Some lwtunnels have a dst cache for post-transformation dst.
If the packet destination did not change we may end up recording
a reference to the lwtunnel in its own cache, and the lwtunnel
state will never be freed.&lt;/p&gt;
&lt;p&gt;Discovered by the ioam6.sh test, kmemleak was recently fixed
to catch per-cpu memory leaks. I&amp;#39;m not sure if rpl and seg6
can actually hit this, but in principle I don&amp;#39;t see why not.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-21768</guid>
    </item>
  </channel>
</rss>
