From: syzbot <syzbot+dec4d528fb7a7c5d8ce3@syzkaller.appspotmail.com>
To: eadavis@sina.com, hdanton@sina.com, johan.hedberg@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, luiz.von.dentz@intel.com,
marcel@holtmann.org, pav@iki.fi, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in __sco_sock_close
Date: Sun, 10 Sep 2023 15:43:38 -0700 [thread overview]
Message-ID: <000000000000dbd624060508f001@google.com> (raw)
In-Reply-To: <0000000000007f826b06044878ed@google.com>
syzbot has bisected this issue to:
commit 94d9ba9f9888b748d4abd2aa1547af56ae85f772
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=124d6578680000
start commit: 99d99825fc07 Merge tag 'nfs-for-6.6-1' of git://git.linux-..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=114d6578680000
console output: https://syzkaller.appspot.com/x/log.txt?x=164d6578680000
kernel config: https://syzkaller.appspot.com/x/.config?x=988789167afa40d5
dashboard link: https://syzkaller.appspot.com/bug?extid=dec4d528fb7a7c5d8ce3
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12e9ba2fa80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=111affcba80000
Reported-by: syzbot+dec4d528fb7a7c5d8ce3@syzkaller.appspotmail.com
Fixes: 94d9ba9f9888 ("Bluetooth: hci_sync: Fix UAF in hci_disconnect_all_sync")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-09-10 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 9:06 [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in __sco_sock_close syzbot
2023-09-01 21:09 ` syzbot
2023-09-10 22:43 ` syzbot [this message]
2023-11-27 7:13 ` 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=000000000000dbd624060508f001@google.com \
--to=syzbot+dec4d528fb7a7c5d8ce3@syzkaller.appspotmail.com \
--cc=eadavis@sina.com \
--cc=hdanton@sina.com \
--cc=johan.hedberg@gmail.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.