<?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-10-03T19:41:39.017862+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-74561</id>
    <title>CVE-2026-74561 — nexthop: avoid unlocked f6i_list walk in nh_rt_cache_flush</title>
    <updated>2026-10-03T19:41:39.454074+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>nexthop: avoid unlocked f6i_list walk in nh_rt_cache_flush</p>
<p>nh_rt_cache_flush() walks nh-&gt;f6i_list during an RTNL-serialized nexthop
replace without holding nh-&gt;lock, racing the unlocked IPv6 route
add/delete that mutate the list under nh-&gt;lock and free fib6_info
entries (nh_rt_cache_flush() is inlined into rtm_new_nexthop()):</p>
<p>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)</p>
<p>Unlike the other f6i_list walks, this one bumps each route's sernum via
fib6_update_sernum_upto_root(), which needs tb6_lock; taking nh-&gt;lock
around it would invert the established tb6_lock -&gt; nh-&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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-74561"/>
  </entry>
</feed>
