All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@idosch.org>
To: syzbot <syzbot+22b2e8ffdc35d97b5942@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, kuznet@ms2.inr.ac.ru,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com, yoshfuji@linux-ipv6.org,
	weiwan@google.com
Subject: Re: KASAN: use-after-free Read in fib6_ifup (2)
Date: Sat, 20 Jan 2018 14:54:51 +0200	[thread overview]
Message-ID: <20180120125451.GA25227@splinter> (raw)
In-Reply-To: <001a11444e645c220905631ac3dc@google.com>

On Thu, Jan 18, 2018 at 09:58:01PM -0800, syzbot wrote:
> Hello,
> 
> syzbot hit the following crash on net-next commit
> 564737f981fb4b4b3266901508bb9b90d9d43de8
> 
> So far this crash happened 18 times on mmots, net-next.
> C reproducer is attached.
> syzkaller reproducer is attached.
> Raw console output is attached.
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached.

[...]

> syzbot will keep track of this bug report.
> If you forgot to add the Reported-by tag, once the fix for this bug is
> merged
> into any tree, please reply to this email with:
> #syz fix: exact-commit-title

The reproducer configures a default source-specific route which triggers
a bug that is now fixed in net-next, so:

#syz fix: ipv6: don't let tb6_root node share routes with other node

Verified it on my machine using the reproducer attached by the bot.

      parent reply	other threads:[~2018-01-20 12:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19  5:58 KASAN: use-after-free Read in fib6_ifup (2) syzbot
2018-01-19 13:19 ` Ido Schimmel
2018-01-20 12:54 ` Ido Schimmel [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=20180120125451.GA25227@splinter \
    --to=idosch@idosch.org \
    --cc=davem@davemloft.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+22b2e8ffdc35d97b5942@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=weiwan@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.