mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@virtuozzo.com>
To: Chen Zhongjin <chenzhongjin@huawei.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, dsahern@kernel.org, daniel@iogearbox.net,
	yangyingliang@huawei.com, stephen@networkplumber.org,
	wangyuweihx@gmail.com, alexander.mikhalitsyn@virtuozzo.com,
	xu.xin16@zte.com.cn
Subject: Re: [PATCH net] net, neigh: Fix null-ptr-deref in neigh_table_clear()
Date: Tue, 1 Nov 2022 13:40:21 +0100	[thread overview]
Message-ID: <56da57f3-446c-fe63-b625-931fd9f0cbd5@virtuozzo.com> (raw)
In-Reply-To: <20221101121552.21890-1-chenzhongjin@huawei.com>

On 11/1/22 13:15, Chen Zhongjin wrote:
> When IPv6 module gets initialized but hits an error in the middle,
> kenel panic with:
>
> KASAN: null-ptr-deref in range [0x0000000000000598-0x000000000000059f]
> CPU: 1 PID: 361 Comm: insmod
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)
> RIP: 0010:__neigh_ifdown.isra.0+0x24b/0x370
> RSP: 0018:ffff888012677908 EFLAGS: 00000202
> ...
> Call Trace:
>   <TASK>
>   neigh_table_clear+0x94/0x2d0
>   ndisc_cleanup+0x27/0x40 [ipv6]
>   inet6_init+0x21c/0x2cb [ipv6]
>   do_one_initcall+0xd3/0x4d0
>   do_init_module+0x1ae/0x670
> ...
> Kernel panic - not syncing: Fatal exception
>
> When ipv6 initialization fails, it will try to cleanup and calls:
>
> neigh_table_clear()
>    neigh_ifdown(tbl, NULL)
>      pneigh_queue_purge(&tbl->proxy_queue, dev_net(dev == NULL))
>      # dev_net(NULL) triggers null-ptr-deref.
>
> Fix it by passing NULL to pneigh_queue_purge() in neigh_ifdown() if dev
> is NULL, to make kernel not panic immediately.
>
> Fixes: 66ba215cb513 ("neigh: fix possible DoS due to net iface start/stop loop")
> Signed-off-by: Chen Zhongjin <chenzhongjin@huawei.com>
> ---
>   net/core/neighbour.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/core/neighbour.c b/net/core/neighbour.c
> index 3c4786b99907..a77a85e357e0 100644
> --- a/net/core/neighbour.c
> +++ b/net/core/neighbour.c
> @@ -409,7 +409,7 @@ static int __neigh_ifdown(struct neigh_table *tbl, struct net_device *dev,
>   	write_lock_bh(&tbl->lock);
>   	neigh_flush_dev(tbl, dev, skip_perm);
>   	pneigh_ifdown_and_unlock(tbl, dev);
> -	pneigh_queue_purge(&tbl->proxy_queue, dev_net(dev));
> +	pneigh_queue_purge(&tbl->proxy_queue, dev ? dev_net(dev) : NULL);
>   	if (skb_queue_empty_lockless(&tbl->proxy_queue))
>   		del_timer_sync(&tbl->proxy_timer);
>   	return 0;
Reviewed-by: Denis V. Lunev <den@openvz.org>

  parent reply	other threads:[~2022-11-01 12:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 12:15 Chen Zhongjin
2022-11-01 12:37 ` Eric Dumazet
2022-11-01 12:40 ` Denis V. Lunev [this message]
2022-11-03  3:50 ` 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=56da57f3-446c-fe63-b625-931fd9f0cbd5@virtuozzo.com \
    --to=den@virtuozzo.com \
    --cc=alexander.mikhalitsyn@virtuozzo.com \
    --cc=chenzhongjin@huawei.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stephen@networkplumber.org \
    --cc=wangyuweihx@gmail.com \
    --cc=xu.xin16@zte.com.cn \
    --cc=yangyingliang@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

all inboxes | Powered by JetHome®