From: David Ahern <dsa@cumulusnetworks.com>
To: Dmitry Vyukov <dvyukov@google.com>,
Mahesh Bandewar <maheshb@google.com>,
Eric Dumazet <edumazet@google.com>,
David Miller <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
James Morris <jmorris@namei.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
Patrick McHardy <kaber@trash.net>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Cong Wang <xiyou.wangcong@gmail.com>
Cc: syzkaller <syzkaller@googlegroups.com>
Subject: Re: net: heap out-of-bounds in fib6_clean_node/rt6_fill_node/fib6_age/fib6_prune_clone
Date: Fri, 3 Mar 2017 11:12:39 -0800 [thread overview]
Message-ID: <f707c195-251f-6058-5f4c-d55710533b11@cumulusnetworks.com> (raw)
In-Reply-To: <CACT4Y+YrA45diWz_8f4St8oX6aTC1kuGXMUvniGRbqXSGwawZQ@mail.gmail.com>
On 3/3/17 6:39 AM, Dmitry Vyukov wrote:
> I am getting heap out-of-bounds reports in
> fib6_clean_node/rt6_fill_node/fib6_age/fib6_prune_clone while running
> syzkaller fuzzer on 86292b33d4b79ee03e2f43ea0381ef85f077c760. They all
> follow the same pattern: an object of size 216 is allocated from
> ip_dst_cache slab, and then accessed at offset 272/276 withing
> fib6_walk. Looks like type confusion. Unfortunately this is not
> reproducible.
I'll take a look this weekend or Monday at the latest.
next prev parent reply other threads:[~2017-03-03 19:40 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 14:39 net: heap out-of-bounds in fib6_clean_node/rt6_fill_node/fib6_age/fib6_prune_clone Dmitry Vyukov
2017-03-03 19:12 ` David Ahern [this message]
2017-03-03 19:14 ` Dmitry Vyukov
2017-03-04 18:57 ` Dmitry Vyukov
2017-03-04 19:00 ` Dmitry Vyukov
2017-03-04 20:15 ` Eric Dumazet
2017-03-05 10:53 ` Dmitry Vyukov
2017-03-06 17:31 ` David Ahern
2017-03-06 18:51 ` Dmitry Vyukov
2017-03-06 23:41 ` David Ahern
2017-03-07 8:43 ` Dmitry Vyukov
2017-03-07 9:21 ` Dmitry Vyukov
2017-03-07 18:03 ` David Ahern
2017-03-07 18:13 ` Dmitry Vyukov
2017-03-07 18:43 ` David Ahern
2017-03-07 19:02 ` Dmitry Vyukov
2017-03-07 19:30 ` Dmitry Vyukov
2017-03-07 20:00 ` Dmitry Vyukov
2017-03-08 11:55 ` Dmitry Vyukov
2017-03-27 12:42 ` Dmitry Vyukov
2017-03-27 13:57 ` David Ahern
2017-03-27 14:23 ` Dmitry Vyukov
2017-04-18 20:43 ` Andrey Konovalov
2017-04-18 23:20 ` David Ahern
2017-04-19 1:09 ` Andrey Konovalov
2017-04-19 16:09 ` David Ahern
2017-04-19 16:12 ` Andrey Konovalov
2017-04-19 16:29 ` David Ahern
2017-04-19 23:47 ` Cong Wang
2017-04-19 23:51 ` David Ahern
2017-04-20 8:35 ` Dmitry Vyukov
2017-04-20 12:10 ` Andrey Konovalov
2017-04-20 15:28 ` Andrey Konovalov
2017-04-20 15:29 ` Andrey Konovalov
2017-04-20 15:35 ` David Ahern
2017-04-20 15:39 ` Andrey Konovalov
2017-04-20 16:09 ` Andrey Konovalov
2017-04-21 14:27 ` David Ahern
2017-04-21 16:47 ` Eric Dumazet
2017-04-21 18:25 ` David Ahern
2017-04-25 15:51 ` David Ahern
2017-04-25 15:57 ` David Ahern
2017-03-07 17:17 ` David Ahern
2017-03-07 17:45 ` Dmitry Vyukov
2017-03-07 17:57 ` David Ahern
2017-04-25 15:56 ` David Ahern
2017-04-25 16:36 ` Andrey Konovalov
2017-04-25 16:38 ` Andrey Konovalov
2017-04-25 16:40 ` David Ahern
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=f707c195-251f-6058-5f4c-d55710533b11@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yoshfuji@linux-ipv6.org \
/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).