<?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-30T15:56:24.412115+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-74581</id>
    <title>CVE-2026-74581 — net: ipv6: clear suppressed fib6 rule result</title>
    <updated>2026-09-30T15:56:24.414096+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>net: ipv6: clear suppressed fib6 rule result</p>
<p>fib6_rule_suppress() drops a suppressed route with ip6_rt_put_flags(),
but leaves res-&gt;rt6 pointing at the released rt6_info.</p>
<p>If no later rule supplies a replacement, fib6_rule_lookup() still sees
res.rt6 and returns that stale dst to its caller. A suppressing rule can
therefore leak a released route back to rt6_lookup(), and the next put
hits rcuref_put_slowpath() from dst_release().</p>
<p>Clear res-&gt;rt6 when suppressing the route so suppressed lookups fall
through to the null dst instead of reusing the released one.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-74581"/>
  </entry>
</feed>
