From: syzbot <syzbot+305a91e025a73e4fd6ce@syzkaller.appspotmail.com>
To: coreteam@netfilter.org, davem@davemloft.net,
devel@driverdev.osuosl.org, eric@anholt.net,
gregkh@linuxfoundation.org, johan.hedberg@gmail.com,
kaber@trash.net, kadlec@blackhole.kfki.hu, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
marcel@holtmann.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in hci_chan_del
Date: Mon, 03 Aug 2020 10:08:06 -0700 [thread overview]
Message-ID: <000000000000a335a405abfc2e1e@google.com> (raw)
In-Reply-To: <000000000000adea7f05abeb19cf@google.com>
syzbot has bisected this issue to:
commit 166beccd47e11e4d27477e8ca1d7eda47cf3b2da
Author: Eric Anholt <eric@anholt.net>
Date: Mon Oct 3 18:52:06 2016 +0000
staging/vchi: Convert to current get_user_pages() arguments.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=178321a4900000
start commit: 5a30a789 Merge tag 'x86-urgent-2020-08-02' of git://git.ke..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=144321a4900000
console output: https://syzkaller.appspot.com/x/log.txt?x=104321a4900000
kernel config: https://syzkaller.appspot.com/x/.config?x=e59ee776d5aa8d55
dashboard link: https://syzkaller.appspot.com/bug?extid=305a91e025a73e4fd6ce
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=127dd914900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=122a94ec900000
Reported-by: syzbot+305a91e025a73e4fd6ce@syzkaller.appspotmail.com
Fixes: 166beccd47e1 ("staging/vchi: Convert to current get_user_pages() arguments.")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-08-03 17:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 20:45 KASAN: use-after-free Read in hci_chan_del syzbot
2020-08-03 17:08 ` syzbot [this message]
2021-05-04 21:50 ` ETenal
2021-05-06 6:01 ` Dan Carpenter
2021-05-06 6:42 ` SyzScope
2021-06-04 9:48 ` Greg KH
2021-06-04 17:11 ` SyzScope
2021-06-05 7:43 ` Greg KH
2021-06-05 18:12 ` SyzScope
2021-06-06 5:16 ` Greg KH
2021-06-06 5:29 ` Leon Romanovsky
2021-06-06 5:06 ` Leon Romanovsky
[not found] ` <20210606085004.12212-1-hdanton@sina.com>
2021-06-06 9:54 ` Greg KH
[not found] ` <20210607074828.3259-1-hdanton@sina.com>
2021-06-07 7:55 ` Greg KH
[not found] ` <20210607100201.3345-1-hdanton@sina.com>
2021-06-07 10:31 ` Greg KH
[not found] ` <20210608081800.3484-1-hdanton@sina.com>
2021-06-08 8:40 ` Greg KH
2021-05-28 21:12 ` SyzScope
2021-06-03 18:30 ` SyzScope
2021-06-03 18:36 ` Greg KH
2021-06-07 10:21 ` Jason A. Donenfeld
2021-06-07 10:28 ` Dmitry Vyukov
2021-06-07 11:20 ` Greg KH
2021-06-07 18:26 ` SyzScope
2021-06-08 8:46 ` Greg KH
2021-06-08 8:53 ` Dan Carpenter
2021-06-07 22:25 ` [syzbot] " syzbot
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=000000000000a335a405abfc2e1e@google.com \
--to=syzbot+305a91e025a73e4fd6ce@syzkaller.appspotmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=gregkh@linuxfoundation.org \
--cc=johan.hedberg@gmail.com \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).