From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
dsahern@kernel.org
Subject: Re: [PATCH net] ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu()
Date: Wed, 04 Mar 2026 01:30:15 +0000 [thread overview]
Message-ID: <177258781504.1546050.15599447015231829493.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260301194548.927324-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 1 Mar 2026 11:45:48 -0800 you wrote:
> l3mdev_master_dev_rcu() can return NULL when the slave device is being
> un-slaved from a VRF. All other callers deal with this, but we lost
> the fallback to loopback in ip6_rt_pcpu_alloc() -> ip6_rt_get_dev_rcu()
> with commit 4832c30d5458 ("net: ipv6: put host and anycast routes on
> device with address").
>
> KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]
> RIP: 0010:ip6_rt_pcpu_alloc (net/ipv6/route.c:1418)
> Call Trace:
> ip6_pol_route (net/ipv6/route.c:2318)
> fib6_rule_lookup (net/ipv6/fib6_rules.c:115)
> ip6_route_output_flags (net/ipv6/route.c:2607)
> vrf_process_v6_outbound (drivers/net/vrf.c:437)
>
> [...]
Here is the summary with links:
- [net] ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu()
https://git.kernel.org/netdev/net/c/2ffb4f5c2ccb
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-03-04 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 19:45 [PATCH net] ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu() Jakub Kicinski
2026-03-02 1:38 ` David Ahern
2026-03-02 14:43 ` Jakub Kicinski
2026-03-03 0:09 ` David Ahern
2026-03-04 1:30 ` 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=177258781504.1546050.15599447015231829493.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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