<?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>Sat, 03 Oct 2026 19:41:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74561 — nexthop: avoid unlocked f6i_list walk in nh_rt_cache_flush</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74561</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;nexthop: avoid unlocked f6i_list walk in nh_rt_cache_flush&lt;/p&gt;
&lt;p&gt;nh_rt_cache_flush() walks nh-&amp;gt;f6i_list during an RTNL-serialized nexthop
replace without holding nh-&amp;gt;lock, racing the unlocked IPv6 route
add/delete that mutate the list under nh-&amp;gt;lock and free fib6_info
entries (nh_rt_cache_flush() is inlined into rtm_new_nexthop()):&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in nh_rt_cache_flush (net/ipv4/nexthop.c:2243)
  Read of size 8 at addr ffff888012953e18 by task exploit/146
   nh_rt_cache_flush (net/ipv4/nexthop.c:2243)
   replace_nexthop (net/ipv4/nexthop.c:2610)
   rtm_new_nexthop (net/ipv4/nexthop.c:3323)
   rtnetlink_rcv_msg (net/core/rtnetlink.c:7076)&lt;/p&gt;
&lt;p&gt;Unlike the other f6i_list walks, this one bumps each route&amp;#39;s sernum via
fib6_update_sernum_upto_root(), which needs tb6_lock; taking nh-&amp;gt;lock
around it would invert the established tb6_lock -&amp;gt; nh-&amp;gt;lock order and
deadlock. As the only purpose is to invalidate cached dsts, bump the
IPv6 sernum for the whole netns with rt_genid_bump_ipv6() instead,
mirroring the rt_cache_flush() already done for IPv4 just above.&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;nexthop: avoid unlocked f6i_list walk in nh_rt_cache_flush&lt;/p&gt;
&lt;p&gt;nh_rt_cache_flush() walks nh-&amp;gt;f6i_list during an RTNL-serialized nexthop
replace without holding nh-&amp;gt;lock, racing the unlocked IPv6 route
add/delete that mutate the list under nh-&amp;gt;lock and free fib6_info
entries (nh_rt_cache_flush() is inlined into rtm_new_nexthop()):&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in nh_rt_cache_flush (net/ipv4/nexthop.c:2243)
  Read of size 8 at addr ffff888012953e18 by task exploit/146
   nh_rt_cache_flush (net/ipv4/nexthop.c:2243)
   replace_nexthop (net/ipv4/nexthop.c:2610)
   rtm_new_nexthop (net/ipv4/nexthop.c:3323)
   rtnetlink_rcv_msg (net/core/rtnetlink.c:7076)&lt;/p&gt;
&lt;p&gt;Unlike the other f6i_list walks, this one bumps each route&amp;#39;s sernum via
fib6_update_sernum_upto_root(), which needs tb6_lock; taking nh-&amp;gt;lock
around it would invert the established tb6_lock -&amp;gt; nh-&amp;gt;lock order and
deadlock. As the only purpose is to invalidate cached dsts, bump the
IPv6 sernum for the whole netns with rt_genid_bump_ipv6() instead,
mirroring the rt_cache_flush() already done for IPv4 just above.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74561</guid>
    </item>
  </channel>
</rss>
