From: patchwork-bot+bluetooth@kernel.org
To: Jia-Hong Su <s11242586@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work
Date: Wed, 21 Jan 2026 21:50:06 +0000 [thread overview]
Message-ID: <176903220634.1456135.14185600440761441438.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260118120859.83680-1-s11242586@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 18 Jan 2026 20:08:59 +0800 you wrote:
> hci_uart_set_proto() sets HCI_UART_PROTO_INIT before calling
> hci_uart_register_dev(), which calls proto->open() to initialize
> hu->priv. However, if a TTY write wakeup occurs during this window,
> hci_uart_tx_wakeup() may schedule write_work before hu->priv is
> initialized, leading to a NULL pointer dereference in
> hci_uart_write_work() when proto->dequeue() accesses hu->priv.
>
> [...]
Here is the summary with links:
- Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work
https://git.kernel.org/bluetooth/bluetooth-next/c/1d8551ecf806
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:[~2026-01-21 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-18 12:08 [PATCH] Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work Jia-Hong Su
2026-01-18 12:50 ` bluez.test.bot
2026-01-21 21:50 ` 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=176903220634.1456135.14185600440761441438.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=s11242586@gmail.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