From: syzbot <syzbot+87badbb9094e008e0685@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, sirdarckcat@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in le_read_features_complete
Date: Mon, 22 Dec 2025 08:37:02 -0800 [thread overview]
Message-ID: <694973ae.050a0220.2fb209.016d.GAE@google.com> (raw)
In-Reply-To: <CACSvzRz6j4cjuLsx=foVSocsD5v6JoWMLGSDF2R92RBtRnVfQw@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+87badbb9094e008e0685@syzkaller.appspotmail.com
Tested-by: syzbot+87badbb9094e008e0685@syzkaller.appspotmail.com
Tested on:
commit: 1abe96e0 Improve fix: properly balance hci_conn_get/pu..
git tree: https://github.com/sirdarckcat/linux-1.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1000808a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e9c74ad1c0c0584
dashboard link: https://syzkaller.appspot.com/bug?extid=87badbb9094e008e0685
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-12-22 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACSvzRz6j4cjuLsx=foVSocsD5v6JoWMLGSDF2R92RBtRnVfQw@mail.gmail.com>
2025-12-22 16:37 ` syzbot [this message]
[not found] <CABBYNZJxEbTZvYNnVK6xFyBXZENFOCmfvWQKqTH6n64t2+9vmw@mail.gmail.com>
2026-03-25 16:47 ` [syzbot] [bluetooth?] KASAN: slab-use-after-free Write in le_read_features_complete syzbot
[not found] <CACSvzRyyBL4RDdvo_DSTjumFfLpy+KiOR92++tV1nzSp-kdzJA@mail.gmail.com>
2025-12-22 16:12 ` syzbot
[not found] <CACSM0CO-32uFHN=d7RArP-go-=RJhvr_VT4d-B34Bapzh0HOtw@mail.gmail.com>
2025-12-16 13:08 ` syzbot
2025-12-08 5:07 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=694973ae.050a0220.2fb209.016d.GAE@google.com \
--to=syzbot+87badbb9094e008e0685@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sirdarckcat@gmail.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.