From: patchwork-bot+netdevbpf@kernel.org
To: Xiang Mei (Microsoft) <xmei5@asu.edu>
Cc: dsahern@kernel.org, idosch@nvidia.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, kuniyu@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
AutonomousCodeSecurity@microsoft.com,
tgopinath@linux.microsoft.com, kys@microsoft.com
Subject: Re: [PATCH net 1/2] nexthop: take nh->lock for f6i_list walks in replace check and notify
Date: Fri, 24 Jul 2026 22:10:22 +0000 [thread overview]
Message-ID: <178493102203.3330129.7311134539620710020.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260722002951.2614721-1-xmei5@asu.edu>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 22 Jul 2026 00:29:50 +0000 you wrote:
> fib6_check_nh_list() and __nexthop_replace_notify() walk nh->f6i_list
> during an RTNL-serialized nexthop replace without holding nh->lock. IPv6
> RTM_NEWROUTE/RTM_DELROUTE run without RTNL and mutate that list under
> nh->lock (fib6_add_rt2node_nh(), fib6_purge_rt()), so both walks race a
> concurrent route delete that unlinks and frees a fib6_info:
>
> BUG: KASAN: slab-use-after-free in rt6_fill_node.isra.0 (net/ipv6/route.c:5799)
> Read of size 4 at addr ffff888014607e64 by task exploit/143
> rt6_fill_node.isra.0 (net/ipv6/route.c:5799)
> fib6_rt_update (net/ipv6/route.c:6412)
> __nexthop_replace_notify (net/ipv4/nexthop.c:2542)
> rtm_new_nexthop (net/ipv4/nexthop.c:2554)
> rtnetlink_rcv_msg (net/core/rtnetlink.c:7076)
>
> [...]
Here is the summary with links:
- [net,1/2] nexthop: take nh->lock for f6i_list walks in replace check and notify
https://git.kernel.org/netdev/net/c/072cd1f21819
- [net,2/2] nexthop: avoid unlocked f6i_list walk in nh_rt_cache_flush
https://git.kernel.org/netdev/net/c/4787a6d2629b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-07-24 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 0:29 [PATCH net 1/2] nexthop: take nh->lock for f6i_list walks in replace check and notify Xiang Mei (Microsoft)
2026-07-22 0:29 ` [PATCH net 2/2] nexthop: avoid unlocked f6i_list walk in nh_rt_cache_flush Xiang Mei (Microsoft)
2026-07-23 19:20 ` Ido Schimmel
2026-07-23 19:19 ` [PATCH net 1/2] nexthop: take nh->lock for f6i_list walks in replace check and notify Ido Schimmel
2026-07-24 22:10 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178493102203.3330129.7311134539620710020.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=AutonomousCodeSecurity@microsoft.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tgopinath@linux.microsoft.com \
--cc=xmei5@asu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox