From: Hangbin Liu <liuhangbin@gmail.com>
To: "Ricardo B. Marlière" <rbm@suse.com>
Cc: "Martin KaFai Lau" <martin.lau@linux.dev>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"John Fastabend" <john.fastabend@gmail.com>,
"Stanislav Fomichev" <sdf@fomichev.me>,
"Alexei Starovoitov" <ast@kernel.org>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Eduard Zingerman" <eddyz87@gmail.com>,
"Song Liu" <song@kernel.org>,
"Yonghong Song" <yonghong.song@linux.dev>,
"KP Singh" <kpsingh@kernel.org>, "Hao Luo" <haoluo@google.com>,
"Jiri Olsa" <jolsa@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"David Ahern" <dsahern@kernel.org>,
"Jay Vosburgh" <jv@jvosburgh.net>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"Fernando Fernandez Mancera" <fmancera@suse.de>,
bpf@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 3/3] net: bonding: Fix nd_tbl NULL dereference when IPv6 is disabled
Date: Fri, 6 Mar 2026 02:31:28 +0000 [thread overview]
Message-ID: <aao8gM6br-_RJ5HO@fedora> (raw)
In-Reply-To: <20260305-net-nd_tbl_fixes-v2-3-b7177db1a9f3@suse.com>
On Thu, Mar 05, 2026 at 05:37:41PM -0300, Ricardo B. Marlière wrote:
> When booting with the 'ipv6.disable=1' parameter, the nd_tbl is never
> initialized because inet6_init() exits before ndisc_init() is called
> which initializes it. If bonding ARP/NS validation is enabled, an IPv6
> NS/NA packet received on a slave can reach bond_validate_na(), which
> calls bond_has_this_ip6(). That path calls ipv6_chk_addr() and can
> crash in __ipv6_chk_addr_and_flags().
>
> BUG: kernel NULL pointer dereference, address: 00000000000005d8
> Oops: Oops: 0000 [#1] SMP NOPTI
> RIP: 0010:__ipv6_chk_addr_and_flags+0x69/0x170
> Call Trace:
> <IRQ>
> ipv6_chk_addr+0x1f/0x30
> bond_validate_na+0x12e/0x1d0 [bonding]
> ? __pfx_bond_handle_frame+0x10/0x10 [bonding]
> bond_rcv_validate+0x1a0/0x450 [bonding]
> bond_handle_frame+0x5e/0x290 [bonding]
> ? srso_alias_return_thunk+0x5/0xfbef5
> __netif_receive_skb_core.constprop.0+0x3e8/0xe50
> ? srso_alias_return_thunk+0x5/0xfbef5
> ? update_cfs_rq_load_avg+0x1a/0x240
> ? srso_alias_return_thunk+0x5/0xfbef5
> ? __enqueue_entity+0x5e/0x240
> __netif_receive_skb_one_core+0x39/0xa0
> process_backlog+0x9c/0x150
> __napi_poll+0x30/0x200
> ? srso_alias_return_thunk+0x5/0xfbef5
> net_rx_action+0x338/0x3b0
> handle_softirqs+0xc9/0x2a0
> do_softirq+0x42/0x60
> </IRQ>
> <TASK>
> __local_bh_enable_ip+0x62/0x70
> __dev_queue_xmit+0x2d3/0x1000
> ? srso_alias_return_thunk+0x5/0xfbef5
> ? srso_alias_return_thunk+0x5/0xfbef5
> ? packet_parse_headers+0x10a/0x1a0
> packet_sendmsg+0x10da/0x1700
> ? kick_pool+0x5f/0x140
> ? srso_alias_return_thunk+0x5/0xfbef5
> ? __queue_work+0x12d/0x4f0
> __sys_sendto+0x1f3/0x220
> __x64_sys_sendto+0x24/0x30
> do_syscall_64+0x101/0xf80
> ? exc_page_fault+0x6e/0x170
> ? srso_alias_return_thunk+0x5/0xfbef5
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> </TASK>
>
> Fix this by adding an early check in bond_confirm_addr6(). If
> ipv6_stub->nd_tbl is NULL, return before calling ipv6_chk_addr().
>
> Suggested-by: Fernando Fernandez Mancera <fmancera@suse.de>
> Fixes: 4e24be018eb9 ("bonding: add new parameter ns_targets")
> Signed-off-by: Ricardo B. Marlière <rbm@suse.com>
> ---
> drivers/net/bonding/bond_main.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
> index 14ed91391fcc..7d32cd231633 100644
> --- a/drivers/net/bonding/bond_main.c
> +++ b/drivers/net/bonding/bond_main.c
> @@ -3256,6 +3256,9 @@ static int bond_confirm_addr6(struct net_device *dev,
> {
> struct in6_addr *addr = (struct in6_addr *)priv->data;
>
> + if (unlikely(!ipv6_mod_enabled()))
> + return 0;
> +
> return ipv6_chk_addr(dev_net(dev), addr, dev, 0);
> }
Hi Ricardo,
Since the ipv6 has been disabled on the host, I'm a little wonder why
don't we check it more early, e.g. in this if check
#if IS_ENABLED(CONFIG_IPV6)
} else if (is_ipv6) {
return bond_na_rcv(skb, bond, slave);
#endif
Thanks
Hangbin
prev parent reply other threads:[~2026-03-06 2:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 20:37 [PATCH net v2 0/3] {net,bpf}: nd_tbl fixes for when ipv6.disable=1 Ricardo B. Marlière
2026-03-05 20:37 ` [PATCH net v2 1/3] bpf: bpf_out_neigh_v4: Fix nd_tbl NULL dereference when IPv6 is disabled Ricardo B. Marlière
2026-03-05 20:37 ` [PATCH net v2 2/3] bpf: bpf_out_neigh_v6: " Ricardo B. Marlière
2026-03-05 21:26 ` Fernando Fernandez Mancera
2026-03-05 20:37 ` [PATCH net v2 3/3] net: bonding: " Ricardo B. Marlière
2026-03-06 2:31 ` Hangbin Liu [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=aao8gM6br-_RJ5HO@fedora \
--to=liuhangbin@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=fmancera@suse.de \
--cc=haoluo@google.com \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=jv@jvosburgh.net \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rbm@suse.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=toke@redhat.com \
--cc=yonghong.song@linux.dev \
/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