From: syzbot <syzbot+56728135217003dc6f7d@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com, davem@davemloft.net,
johan.hedberg@gmail.com, kuba@kernel.org, linma@zju.edu.cn,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, marcel@holtmann.org,
netdev@vger.kernel.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] kernel panic: stack is corrupted in debug_object_active_state
Date: Sat, 16 Aug 2025 23:18:04 -0700 [thread overview]
Message-ID: <68a1741c.050a0220.e29e5.005d.GAE@google.com> (raw)
In-Reply-To: <689ff66d.050a0220.e29e5.0036.GAE@google.com>
syzbot has bisected this issue to:
commit e305509e678b3a4af2b3cfd410f409f7cdaabb52
Author: Lin Ma <linma@zju.edu.cn>
Date: Sun May 30 13:37:43 2021 +0000
Bluetooth: use correct lock to prevent UAF of hdev object
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10c6e234580000
start commit: ee94b00c1a64 Merge tag 'block-6.17-20250815' of git://git...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=12c6e234580000
console output: https://syzkaller.appspot.com/x/log.txt?x=14c6e234580000
kernel config: https://syzkaller.appspot.com/x/.config?x=98e114f4eb77e551
dashboard link: https://syzkaller.appspot.com/bug?extid=56728135217003dc6f7d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=118d2234580000
Reported-by: syzbot+56728135217003dc6f7d@syzkaller.appspotmail.com
Fixes: e305509e678b ("Bluetooth: use correct lock to prevent UAF of hdev object")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-08-17 6:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 3:09 [syzbot] [ntfs3?] kernel panic: stack is corrupted in debug_object_active_state syzbot
2025-08-17 6:18 ` 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=68a1741c.050a0220.e29e5.005d.GAE@google.com \
--to=syzbot+56728135217003dc6f7d@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=davem@davemloft.net \
--cc=johan.hedberg@gmail.com \
--cc=kuba@kernel.org \
--cc=linma@zju.edu.cn \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--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.