From: syzbot <syzbot+495688b736534bb6c6ad@syzkaller.appspotmail.com>
To: alex.aring@gmail.com, davem@davemloft.net, jiri@mellanox.com,
linux-kernel@vger.kernel.org, linux-wpan@vger.kernel.org,
netdev@vger.kernel.org, stefan@datenfreihafen.org,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in nl8NUM_dump_wpan_phy
Date: Tue, 08 Oct 2019 18:24:00 -0700 [thread overview]
Message-ID: <000000000000c1f845059470233a@google.com> (raw)
In-Reply-To: <000000000000ba89a9059456a51f@google.com>
syzbot has bisected this bug to:
commit 75cdbdd089003cd53560ff87b690ae911fa7df8e
Author: Jiri Pirko <jiri@mellanox.com>
Date: Sat Oct 5 18:04:37 2019 +0000
net: ieee802154: have genetlink code to parse the attrs during dumpit
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14620210e00000
start commit: 056ddc38 Merge branch 'stmmac-next'
git tree: net-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=16620210e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=12620210e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=d9be300620399522
dashboard link: https://syzkaller.appspot.com/bug?extid=495688b736534bb6c6ad
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e256c3600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=175ecdfb600000
Reported-by: syzbot+495688b736534bb6c6ad@syzkaller.appspotmail.com
Fixes: 75cdbdd08900 ("net: ieee802154: have genetlink code to parse the
attrs during dumpit")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-10-09 1:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 18:59 KASAN: use-after-free Read in nl8NUM_dump_wpan_phy syzbot
2019-10-09 1:24 ` syzbot [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=000000000000c1f845059470233a@google.com \
--to=syzbot+495688b736534bb6c6ad@syzkaller.appspotmail.com \
--cc=alex.aring@gmail.com \
--cc=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stefan@datenfreihafen.org \
--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 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).