From: syzbot <syzbot+cf54c1da6574b6c1b049@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com,
johan.hedberg@gmail.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
lrh2000@pku.edu.cn, luiz.dentz@gmail.com,
luiz.von.dentz@intel.com, marcel@holtmann.org,
netdev@vger.kernel.org, pabeni@redhat.com, pav@iki.fi,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in sco_chan_del
Date: Thu, 17 Aug 2023 21:39:36 -0700 [thread overview]
Message-ID: <000000000000a8c57a06032b1dd2@google.com> (raw)
In-Reply-To: <00000000000013b93805fbbadc50@google.com>
syzbot has bisected this issue to:
commit 45c37c4e9c9aab5bb1cf5778d8e5ebd9f9ad820a
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: Wed Aug 9 23:49:33 2023 +0000
Bluetooth: hci_sync: Fix UAF in hci_disconnect_all_sync
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1331e265a80000
start commit: 47762f086974 Add linux-next specific files for 20230817
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=10b1e265a80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1731e265a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ed03cf326b3ef94c
dashboard link: https://syzkaller.appspot.com/bug?extid=cf54c1da6574b6c1b049
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1125bc65a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14ce8f03a80000
Reported-by: syzbot+cf54c1da6574b6c1b049@syzkaller.appspotmail.com
Fixes: 45c37c4e9c9a ("Bluetooth: hci_sync: Fix UAF in hci_disconnect_all_sync")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-08-18 4:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 12:47 [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in sco_chan_del syzbot
2023-05-15 16:01 ` Ruihan Li
2023-08-17 12:56 ` syzbot
2023-08-18 4:39 ` 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=000000000000a8c57a06032b1dd2@google.com \
--to=syzbot+cf54c1da6574b6c1b049@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrh2000@pku.edu.cn \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pav@iki.fi \
--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).