From: shaurya <ssranevjti@gmail.com>
To: syzbot+14b6d57fb728e27ce23c@syzkaller.appspotmail.com
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
luiz.dentz@gmail.com, marcel@holtmann.org, ssranevjti@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in l2cap_unregister_user
Date: Thu, 6 Nov 2025 00:33:57 +0530 [thread overview]
Message-ID: <ecb7b4e7-5006-4642-8807-01b764cd4b2b@gmail.com> (raw)
In-Reply-To: <690b6df3.050a0220.2e3c35.000a.GAE@google.com>
#syz test:
https://lore.kernel.org/all/20251105142251.101852-1-ssranevjti@gmail.com/T/
next prev parent reply other threads:[~2025-11-05 19:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 14:22 [PATCH] Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user ssrane_b23
2025-11-05 14:40 ` shaurya
2025-11-05 15:32 ` [syzbot] [bluetooth?] KASAN: slab-use-after-free Read " syzbot
2025-11-05 19:03 ` shaurya [this message]
2025-11-05 19:04 ` syzbot
2025-11-05 19:05 ` shaurya
2025-11-05 19:05 ` syzbot
2025-11-05 19:26 ` [PATCH] Bluetooth: L2CAP: Fix use-after-free " shaurya
2025-11-05 20:14 ` [syzbot] [bluetooth?] KASAN: slab-use-after-free Read " syzbot
2025-11-05 19:36 ` [PATCH] Bluetooth: L2CAP: Fix use-after-free " Pauli Virtanen
2025-11-06 18:20 ` [PATCH v2 1/1] " ssrane_b23
[not found] <5c93792d0d75a84b0df4f9828d20f33c7a1e71fb.camel@iki.fi>
2026-03-07 11:00 ` [syzbot] [bluetooth?] KASAN: slab-use-after-free Read " syzbot
[not found] <a36a0c60c12b6a8e09776875f2836f2e03894639.camel@iki.fi>
2026-03-07 10:22 ` syzbot
[not found] <625d3721ef07c7c15488af80fbfc53620921611b.camel@iki.fi>
2026-03-07 9:33 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2024-11-01 18:29 syzbot
2024-11-02 1:27 ` Hillf Danton
2024-11-02 1:46 ` syzbot
2024-12-23 22:29 ` syzbot
2025-08-12 16:31 ` syzbot
2025-08-13 1:46 ` Hillf Danton
2025-08-13 2:41 ` 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=ecb7b4e7-5006-4642-8807-01b764cd4b2b@gmail.com \
--to=ssranevjti@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=syzbot+14b6d57fb728e27ce23c@syzkaller.appspotmail.com \
--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