From: patchwork-bot+bluetooth@kernel.org
To: Ivan Pravdin <ipravdin.official@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, mmandlik@google.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+4ed6852d4da4606c93da@syzkaller.appspotmail.com
Subject: Re: [PATCH bluetooth-next] Bluetooth: bcsp: receive data only if registered
Date: Tue, 09 Sep 2025 21:00:07 +0000 [thread overview]
Message-ID: <175745160701.815420.2318120410651085608.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250830200339.36429-2-ipravdin.official@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 30 Aug 2025 16:03:40 -0400 you wrote:
> Currently, bcsp_recv() can be called even when the BCSP protocol has not
> been registered. This leads to a NULL pointer dereference, as shown in
> the following stack trace:
>
> KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]
> RIP: 0010:bcsp_recv+0x13d/0x1740 drivers/bluetooth/hci_bcsp.c:590
> Call Trace:
> <TASK>
> hci_uart_tty_receive+0x194/0x220 drivers/bluetooth/hci_ldisc.c:627
> tiocsti+0x23c/0x2c0 drivers/tty/tty_io.c:2290
> tty_ioctl+0x626/0xde0 drivers/tty/tty_io.c:2706
> vfs_ioctl fs/ioctl.c:51 [inline]
> __do_sys_ioctl fs/ioctl.c:907 [inline]
> __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
> [...]
Here is the summary with links:
- [bluetooth-next] Bluetooth: bcsp: receive data only if registered
https://git.kernel.org/bluetooth/bluetooth-next/c/6c7e4432e56e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-09-09 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 20:03 Ivan Pravdin
2025-09-09 21:00 ` patchwork-bot+bluetooth [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=175745160701.815420.2318120410651085608.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=ipravdin.official@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mmandlik@google.com \
--cc=syzbot+4ed6852d4da4606c93da@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®