From: Simon Horman <horms@kernel.org>
To: Wang Liang <wangliang74@huawei.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, dsahern@kernel.org,
gnault@redhat.com, daniel@iogearbox.net, fw@strlen.de,
yuehaibing@huawei.com, zhangchangzhong@huawei.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net: fix NULL pointer dereference in l3mdev_l3_rcv
Date: Sun, 23 Mar 2025 19:35:38 +0000 [thread overview]
Message-ID: <20250323193538.GD892515@horms.kernel.org> (raw)
In-Reply-To: <20250321090353.1170545-1-wangliang74@huawei.com>
On Fri, Mar 21, 2025 at 05:03:53PM +0800, Wang Liang wrote:
> When delete l3s ipvlan:
>
> ip link del link eth0 ipvlan1 type ipvlan mode l3s
>
> This may cause a null pointer dereference:
>
> Call trace:
> ip_rcv_finish+0x48/0xd0
> ip_rcv+0x5c/0x100
> __netif_receive_skb_one_core+0x64/0xb0
> __netif_receive_skb+0x20/0x80
> process_backlog+0xb4/0x204
> napi_poll+0xe8/0x294
> net_rx_action+0xd8/0x22c
> __do_softirq+0x12c/0x354
>
> This is because l3mdev_l3_rcv() visit dev->l3mdev_ops after
> ipvlan_l3s_unregister() assign the dev->l3mdev_ops to NULL. The process
> like this:
>
> (CPU1) | (CPU2)
> l3mdev_l3_rcv() |
> check dev->priv_flags: |
> master = skb->dev; |
> |
> | ipvlan_l3s_unregister()
> | set dev->priv_flags
> | dev->l3mdev_ops = NULL;
> |
> visit master->l3mdev_ops |
>
> To avoid this by do not set dev->l3mdev_ops when unregister l3s ipvlan.
>
> Suggested-by: David Ahern <dsahern@kernel.org>
> Fixes: c675e06a98a4 ("ipvlan: decouple l3s mode dependencies from other modes")
> Signed-off-by: Wang Liang <wangliang74@huawei.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-03-23 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 9:03 [PATCH net v2] net: fix NULL pointer dereference in l3mdev_l3_rcv Wang Liang
2025-03-23 19:35 ` Simon Horman [this message]
2025-03-25 15:30 ` patchwork-bot+netdevbpf
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=20250323193538.GD892515@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=gnault@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wangliang74@huawei.com \
--cc=yuehaibing@huawei.com \
--cc=zhangchangzhong@huawei.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;
as well as URLs for NNTP newsgroup(s).