From: David Miller <davem@davemloft.net>
To: dsa@cumulusnetworks.com
Cc: xiyou.wangcong@gmail.com, netdev@vger.kernel.org,
andreyknvl@google.com, eric.dumazet@gmail.com
Subject: Re: [Patch net v3] ipv6: check for ip6_null_entry in __ip6_del_rt_siblings()
Date: Thu, 02 Mar 2017 12:45:03 -0800 (PST) [thread overview]
Message-ID: <20170302.124503.746554950603549261.davem@davemloft.net> (raw)
In-Reply-To: <8a8f59e9-c2b4-d630-4cc7-faf7172773be@cumulusnetworks.com>
From: David Ahern <dsa@cumulusnetworks.com>
Date: Wed, 1 Mar 2017 15:03:45 -0800
> On 2/27/17 4:07 PM, Cong Wang wrote:
>> Andrey reported a NULL pointer deref bug in ipv6_route_ioctl()
>> -> ip6_route_del() -> __ip6_del_rt_siblings() code path. This is
>> because ip6_null_entry is returned in this path since ip6_null_entry
>> is kinda default for a ipv6 route table root node. Quote from
>> David Ahern:
>>
>> ip6_null_entry is the root of all ipv6 fib tables making it integrated
>> into the table ...
>>
>> We should ignore any attempt of trying to delete it, like we do in
>> __ip6_del_rt() path and several others.
>>
>> Reported-by: Andrey Konovalov <andreyknvl@google.com>
>> Fixes: 0ae8133586ad ("net: ipv6: Allow shorthand delete of all nexthops in multipath route")
>> Cc: David Ahern <dsa@cumulusnetworks.com>
>> Cc: Eric Dumazet <eric.dumazet@gmail.com>
>> Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
>> ---
>> net/ipv6/route.c | 14 +++++++++-----
>> 1 file changed, 9 insertions(+), 5 deletions(-)
>
>
> Acked-by: David Ahern <dsa@cumulusnetworks.com>
Applied, thanks.
prev parent reply other threads:[~2017-03-02 20:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 0:07 [Patch net v3] ipv6: check for ip6_null_entry in __ip6_del_rt_siblings() Cong Wang
2017-02-28 0:14 ` David Ahern
2017-02-28 0:40 ` Cong Wang
2017-03-01 23:16 ` Martin KaFai Lau
2017-03-01 23:22 ` David Ahern
2017-03-02 0:07 ` David Ahern
2017-03-02 0:42 ` Martin KaFai Lau
2017-03-02 5:06 ` David Ahern
2017-03-01 23:03 ` David Ahern
2017-03-02 20:45 ` David Miller [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=20170302.124503.746554950603549261.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andreyknvl@google.com \
--cc=dsa@cumulusnetworks.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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).