From: Simon Horman <horms@kernel.org>
To: Wang Liang <wangliang74@huawei.com>
Cc: dsahern@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, fw@strlen.de,
daniel@iogearbox.net, yuehaibing@huawei.com,
zhangchangzhong@huawei.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: fix NULL pointer dereference in l3mdev_l3_rcv
Date: Tue, 18 Mar 2025 14:38:00 +0000 [thread overview]
Message-ID: <20250318143800.GA688833@kernel.org> (raw)
In-Reply-To: <20250313012713.748006-1-wangliang74@huawei.com>
On Thu, Mar 13, 2025 at 09:27:13AM +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 |
>
> Add lock for dev->priv_flags and dev->l3mdev_ops is too expensive. Resolve
> this issue by add check for master->l3mdev_ops.
Hi Wang Liang,
It seems to me that checking master->l3mdev_ops like this is racy.
>
> Fixes: c675e06a98a4 ("ipvlan: decouple l3s mode dependencies from other modes")
> Signed-off-by: Wang Liang <wangliang74@huawei.com>
> ---
> include/net/l3mdev.h | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/include/net/l3mdev.h b/include/net/l3mdev.h
> index f7fe796e8429..b5af87a35a9f 100644
> --- a/include/net/l3mdev.h
> +++ b/include/net/l3mdev.h
> @@ -165,6 +165,7 @@ static inline
> struct sk_buff *l3mdev_l3_rcv(struct sk_buff *skb, u16 proto)
> {
> struct net_device *master = NULL;
> + const struct l3mdev_ops *l3mdev_ops;
If you end up respinning for some other reason, please rearrange the lines
above in reverse xmas tree order - longest line to shortest.
>
> if (netif_is_l3_slave(skb->dev))
> master = netdev_master_upper_dev_get_rcu(skb->dev);
> @@ -172,8 +173,12 @@ struct sk_buff *l3mdev_l3_rcv(struct sk_buff *skb, u16 proto)
> netif_has_l3_rx_handler(skb->dev))
> master = skb->dev;
>
> - if (master && master->l3mdev_ops->l3mdev_l3_rcv)
> - skb = master->l3mdev_ops->l3mdev_l3_rcv(master, skb, proto);
> + if (!master)
> + return skb;
> +
> + l3mdev_ops = master->l3mdev_ops;
> + if (l3mdev_ops && l3mdev_ops->l3mdev_l3_rcv)
> + skb = l3mdev_ops->l3mdev_l3_rcv(master, skb, proto);
>
> return skb;
> }
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-03-18 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 1:27 [PATCH net] net: fix NULL pointer dereference in l3mdev_l3_rcv Wang Liang
2025-03-18 14:38 ` Simon Horman [this message]
2025-03-18 15:02 ` David Ahern
2025-03-19 2:07 ` Wang Liang
2025-03-19 2:08 ` David Ahern
2025-03-20 13:37 ` Simon Horman
2025-03-21 8:51 ` Wang Liang
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=20250318143800.GA688833@kernel.org \
--to=horms@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--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).