From: syzbot <syzbot+077eca30d3cb7c02b273@syzkaller.appspotmail.com>
To: anmol.karan123@gmail.com, coreteam@netfilter.org,
davem@davemloft.net, devel@driverdev.osuosl.org,
foxhlchen@gmail.com, 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,
linux-media@vger.kernel.org, marcel@holtmann.org,
mchehab@kernel.org, mchehab@s-opensource.com,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
pablo@netfilter.org, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Write in __sco_sock_close
Date: Tue, 15 Dec 2020 23:15:03 -0800 [thread overview]
Message-ID: <0000000000004ea4fe05b68fa299@google.com> (raw)
In-Reply-To: <000000000000ab11c505abeb19f5@google.com>
syzbot suspects this issue was fixed by commit:
commit 6dfccd13db2ff2b709ef60a50163925d477549aa
Author: Anmol Karn <anmol.karan123@gmail.com>
Date: Wed Sep 30 14:18:13 2020 +0000
Bluetooth: Fix null pointer dereference in hci_event_packet()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14cb845b500000
start commit: 47ec5303 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=e0c783f658542f35
dashboard link: https://syzkaller.appspot.com/bug?extid=077eca30d3cb7c02b273
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=165a89dc900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=130a8c62900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: Bluetooth: Fix null pointer dereference in hci_event_packet()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-12-16 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 20:45 KASAN: use-after-free Write in __sco_sock_close syzbot
2020-08-03 0:49 ` syzbot
2020-12-16 7:15 ` syzbot [this message]
2020-12-17 11:07 ` 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=0000000000004ea4fe05b68fa299@google.com \
--to=syzbot+077eca30d3cb7c02b273@syzkaller.appspotmail.com \
--cc=anmol.karan123@gmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=foxhlchen@gmail.com \
--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=linux-media@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mchehab@kernel.org \
--cc=mchehab@s-opensource.com \
--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