From: Florian Westphal <fw@strlen.de>
To: syzbot <syzbot+9d971dd21eb26567036b@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, herbert@gondor.apana.org.au,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
steffen.klassert@secunet.com, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Write in __xfrm_policy_unlink
Date: Wed, 26 Dec 2018 11:42:21 +0100 [thread overview]
Message-ID: <20181226104221.pojiahsinsspkkxf@breakpoint.cc> (raw)
In-Reply-To: <0000000000003878ad057d97d241@google.com>
syzbot <syzbot+9d971dd21eb26567036b@syzkaller.appspotmail.com> wrote:
> syzbot has found a reproducer for the following crash on:
>
> HEAD commit: ce28bb445388 Merge git://git.kernel.org/pub/scm/linux/kern..
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1673fb1b400000
> kernel config: https://syzkaller.appspot.com/x/.config?x=67a2081147a23142
> dashboard link: https://syzkaller.appspot.com/bug?extid=9d971dd21eb26567036b
> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1134dcc7400000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=126986ed400000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+9d971dd21eb26567036b@syzkaller.appspotmail.com
I've fixed this one. Chances are that at least some of the other
reports are duplicates of this one.
I will continue to look at other reports over the next few days and plan
to send out fixes and test cases next week.
next prev parent reply other threads:[~2018-12-26 10:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 8:50 KASAN: use-after-free Write in __xfrm_policy_unlink syzbot
2018-12-20 23:04 ` syzbot
2018-12-22 8:05 ` syzbot
2018-12-26 10:42 ` Florian Westphal [this message]
2018-12-27 10:17 ` Dmitry Vyukov
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=20181226104221.pojiahsinsspkkxf@breakpoint.cc \
--to=fw@strlen.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=syzbot+9d971dd21eb26567036b@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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 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.