netdev - Re: [PATCH] net/neighbour: fix potential null pointer deference

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <15960edf-b5b7-ea53-c48a-e459280547a6@gmail.com>
Date:   Fri, 31 May 2019 07:56:09 -0700
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     Young Xiao <92siuyang@...il.com>, davem@...emloft.net,
        dsahern@...il.com, roopa@...ulusnetworks.com, christian@...uner.io,
        khlebnikov@...dex-team.ru, netdev@...r.kernel.org
Subject: Re: [PATCH] net/neighbour: fix potential null pointer deference



On 5/31/19 1:29 AM, Young Xiao wrote:
> There is a possible null pointer deference bugs in neigh_fill_info(),
> which is similar to the bug which was fixed in commit 6adc5fd6a142
> ("net/neighbour: fix crash at dumping device-agnostic proxy entries").
> 
> Signed-off-by: Young Xiao <92siuyang@...il.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 dfa8710..33c3ff1 100644
> --- a/net/core/neighbour.c
> +++ b/net/core/neighbour.c
> @@ -2440,7 +2440,7 @@ static int neigh_fill_info(struct sk_buff *skb, struct neighbour *neigh,
>  	ndm->ndm_pad2    = 0;
>  	ndm->ndm_flags	 = neigh->flags;
>  	ndm->ndm_type	 = neigh->type;
> -	ndm->ndm_ifindex = neigh->dev->ifindex;
> +	ndm->ndm_ifindex = neigh->dev ? neigh->dev->ifindex : 0;
>  
>  	if (nla_put(skb, NDA_DST, neigh->tbl->key_len, neigh->primary_key))
>  		goto nla_put_failure;
> 

When was the bug added exactly ?

Hint : We want a Fixes: tag, so that we can fully understand the issue and make sure the
fix is complete.

Otherwise, your patch might very well have been randomly generated by a bot.

Thank you.