From: syzbot <syzbot+1683f76f1b20b826de67@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, hdanton@sina.com,
johan.hedberg@gmail.com, kuba@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
lizhi.xu@windriver.com, luiz.dentz@gmail.com,
luiz.von.dentz@intel.com, marcel@holtmann.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, verdre@v0yd.nl
Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in hci_conn_drop (2)
Date: Sat, 17 Feb 2024 11:33:03 -0800 [thread overview]
Message-ID: <000000000000d77a69061198ed40@google.com> (raw)
In-Reply-To: <000000000000e69b5a06093287ec@google.com>
syzbot has bisected this issue to:
commit 456561ba8e495e9320c1f304bf1cd3d1043cbe7b
Author: Jonas Dreßler <verdre@v0yd.nl>
Date: Tue Feb 6 11:08:13 2024 +0000
Bluetooth: hci_conn: Only do ACL connections sequentially
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=132137fc180000
start commit: 2c3b09aac00d Add linux-next specific files for 20240214
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=10a137fc180000
console output: https://syzkaller.appspot.com/x/log.txt?x=172137fc180000
kernel config: https://syzkaller.appspot.com/x/.config?x=176d2dcbf8ba7017
dashboard link: https://syzkaller.appspot.com/bug?extid=1683f76f1b20b826de67
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1765258a180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16c27a58180000
Reported-by: syzbot+1683f76f1b20b826de67@syzkaller.appspotmail.com
Fixes: 456561ba8e49 ("Bluetooth: hci_conn: Only do ACL connections sequentially")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-02-17 19:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 22:01 [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in hci_conn_drop (2) syzbot
2023-11-03 1:01 ` [syzbot] test uaf in hci_conn_drop syzbot
2023-11-03 5:13 ` syzbot
2023-11-03 7:01 ` syzbot
2023-11-03 8:00 ` syzbot
2023-11-04 3:23 ` syzbot
2023-11-04 4:47 ` syzbot
2023-11-04 5:40 ` syzbot
2024-02-17 2:09 ` [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in hci_conn_drop (2) syzbot
2024-02-17 10:57 ` Hillf Danton
2024-02-17 11:23 ` syzbot
2024-02-18 8:44 ` Hillf Danton
2024-02-18 8:46 ` syzbot
2024-02-17 19:33 ` syzbot [this message]
[not found] <20231103010143.3182694-1-lizhi.xu@windriver.com>
2023-11-03 3:54 ` syzbot
[not found] <20231103051306.721321-1-lizhi.xu@windriver.com>
2023-11-03 5:23 ` syzbot
[not found] <20231103070111.2610655-1-lizhi.xu@windriver.com>
2023-11-03 7:11 ` syzbot
[not found] <20231103080016.3516726-1-lizhi.xu@windriver.com>
2023-11-03 8:17 ` syzbot
[not found] <20231103121804.1421-1-hdanton@sina.com>
2023-11-03 12:43 ` syzbot
[not found] <20231104032323.2233372-1-lizhi.xu@windriver.com>
2023-11-04 3:36 ` syzbot
[not found] <20231104044729.2716748-1-lizhi.xu@windriver.com>
2023-11-04 5:17 ` syzbot
[not found] <20231104054009.3030149-1-lizhi.xu@windriver.com>
2023-11-04 6:00 ` 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=000000000000d77a69061198ed40@google.com \
--to=syzbot+1683f76f1b20b826de67@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--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=syzkaller-bugs@googlegroups.com \
--cc=verdre@v0yd.nl \
/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