From: Eric Biggers <ebiggers@kernel.org>
To: syzbot <syzbot+e9abaabc441d3dd18735@syzkaller.appspotmail.com>
Cc: johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, luiz.dentz@gmail.com,
marcel@holtmann.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in l2cap_connect_cfm
Date: Fri, 7 Mar 2025 00:25:38 +0000 [thread overview]
Message-ID: <20250307002538.GA302609@google.com> (raw)
In-Reply-To: <67ca3c79.050a0220.15b4b9.0072.GAE@google.com>
On Thu, Mar 06, 2025 at 04:23:21PM -0800, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: f66d6acccbc0 Merge tag 'x86_urgent_for_v6.12' of git://git..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1666b2e8580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=ca2f08f822652bd0
> dashboard link: https://syzkaller.appspot.com/bug?extid=e9abaabc441d3dd18735
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
>
> Unfortunately, I don't have any reproducer for this issue yet.
Maybe this will stop the spam:
#syz invalid
next prev parent reply other threads:[~2025-03-07 0:26 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 17:58 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in l2cap_connect_cfm syzbot
2025-03-06 17:41 ` syzbot
2025-03-06 17:42 ` syzbot
2025-03-06 17:43 ` syzbot
2025-03-06 17:44 ` syzbot
2025-03-06 17:45 ` syzbot
2025-03-06 17:46 ` syzbot
2025-03-06 17:47 ` syzbot
2025-03-06 17:48 ` syzbot
2025-03-06 17:49 ` syzbot
2025-03-06 17:50 ` syzbot
2025-03-06 17:51 ` syzbot
2025-03-06 17:52 ` syzbot
2025-03-06 17:53 ` syzbot
2025-03-06 17:54 ` syzbot
2025-03-06 17:55 ` syzbot
2025-03-06 17:56 ` syzbot
2025-03-06 17:57 ` syzbot
2025-03-06 17:58 ` syzbot
2025-03-06 17:59 ` syzbot
2025-03-06 18:00 ` syzbot
2025-03-06 18:01 ` syzbot
2025-03-06 18:02 ` syzbot
2025-03-06 18:03 ` syzbot
2025-03-06 18:04 ` syzbot
2025-03-06 18:05 ` syzbot
2025-03-06 18:06 ` syzbot
2025-03-06 18:07 ` syzbot
2025-03-07 0:00 ` syzbot
2025-03-07 0:01 ` syzbot
2025-03-07 0:02 ` syzbot
2025-03-07 0:03 ` syzbot
2025-03-07 0:04 ` syzbot
2025-03-07 0:05 ` syzbot
2025-03-07 0:06 ` syzbot
2025-03-07 0:07 ` syzbot
2025-03-07 0:08 ` syzbot
2025-03-07 0:09 ` syzbot
2025-03-07 0:10 ` syzbot
2025-03-07 0:11 ` syzbot
2025-03-07 0:12 ` syzbot
2025-03-07 0:13 ` syzbot
2025-03-07 0:14 ` syzbot
2025-03-07 0:15 ` syzbot
2025-03-07 0:16 ` syzbot
2025-03-07 0:17 ` syzbot
2025-03-07 0:18 ` syzbot
2025-03-07 0:19 ` syzbot
2025-03-07 0:20 ` syzbot
2025-03-07 0:21 ` syzbot
2025-03-07 0:22 ` syzbot
2025-03-07 0:23 ` syzbot
2025-03-07 0:25 ` Eric Biggers [this message]
2025-03-07 0:24 ` syzbot
2025-03-07 0:25 ` 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=20250307002538.GA302609@google.com \
--to=ebiggers@kernel.org \
--cc=johan.hedberg@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+e9abaabc441d3dd18735@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 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.