From: syzbot <syzbot+683f8cb11b94b1824c77@syzkaller.appspotmail.com>
To: avkrasnov@salutedevices.com, hdanton@sina.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, luiz.von.dentz@intel.com,
marcel@holtmann.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in skb_queue_purge_reason (2)
Date: Mon, 10 Feb 2025 03:26:02 -0800 [thread overview]
Message-ID: <67a9e24a.050a0220.3d72c.0050.GAE@google.com> (raw)
In-Reply-To: <000000000000cbc8670618a25b24@google.com>
syzbot has bisected this issue to:
commit c411c62cc13319533b1861e00cedc4883c3bc1bb
Author: Arseniy Krasnov <avkrasnov@salutedevices.com>
Date: Thu Jan 30 18:43:26 2025 +0000
Bluetooth: hci_uart: fix race during initialization
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=116cebdf980000
start commit: 40b8e93e17bf Add linux-next specific files for 20250204
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=136cebdf980000
console output: https://syzkaller.appspot.com/x/log.txt?x=156cebdf980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ec880188a87c6aad
dashboard link: https://syzkaller.appspot.com/bug?extid=683f8cb11b94b1824c77
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10b7eeb0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12f74f64580000
Reported-by: syzbot+683f8cb11b94b1824c77@syzkaller.appspotmail.com
Fixes: c411c62cc133 ("Bluetooth: hci_uart: fix race during initialization")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-02-10 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 8:44 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in skb_queue_purge_reason (2) syzbot
2025-02-04 14:48 ` syzbot
2025-02-10 11:26 ` syzbot [this message]
2025-02-11 14:16 ` [DMARC error] " Arseniy Krasnov
2025-02-11 16:22 ` Arseniy Krasnov
2025-02-11 16:51 ` Luiz Augusto von Dentz
2025-02-12 6:05 ` Arseniy Krasnov
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=67a9e24a.050a0220.3d72c.0050.GAE@google.com \
--to=syzbot+683f8cb11b94b1824c77@syzkaller.appspotmail.com \
--cc=avkrasnov@salutedevices.com \
--cc=hdanton@sina.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.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).