From: patchwork-bot+bluetooth@kernel.org
To: w15303746062 <w15303746062@163.com>
Cc: luiz.dentz@gmail.com, pmenzel@molgen.mpg.de, marcel@holtmann.org,
linux-bluetooth@vger.kernel.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org, greg@kroah.com,
stable@vger.kernel.org, 25181214217@stu.xidian.edu.cn
Subject: Re: [PATCH v9] Bluetooth: hci_uart: fix UAFs and race conditions in close and init paths
Date: Tue, 19 May 2026 15:00:04 +0000 [thread overview]
Message-ID: <177920280488.2756414.8251481561878776667.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260518024949.439299-1-w15303746062@163.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 18 May 2026 10:49:49 +0800 you wrote:
> From: Mingyu Wang <25181214217@stu.xidian.edu.cn>
>
> Vulnerabilities leading to Use-After-Free (UAF) and Null Pointer
> Dereference (NPD) conditions were observed in the lifecycle management
> of hci_uart.
>
> The primary issue arises because the workqueues (init_ready and
> write_work) are only flushed/cancelled if the HCI_UART_PROTO_READY
> flag is set during TTY close. If a hangup occurs before setup completes,
> hci_uart_tty_close() skips the teardown of these workqueues and
> proceeds to free the `hu` struct. When the scheduled work executes
> later, it blindly dereferences the freed `hu` struct.
>
> [...]
Here is the summary with links:
- [v9] Bluetooth: hci_uart: fix UAFs and race conditions in close and init paths
https://git.kernel.org/bluetooth/bluetooth-next/c/7db62a762f61
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-05-19 14:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 6:45 [PATCH] Bluetooth: hci_uart: fix UAF in hci_uart_tty_close() w15303746062
2026-05-13 9:04 ` Paul Menzel
2026-05-14 15:17 ` [PATCH v2] " w15303746062
2026-05-15 6:10 ` Greg KH
2026-05-15 6:50 ` [PATCH v3] " w15303746062
2026-05-15 12:37 ` [PATCH] " Luiz Augusto von Dentz
2026-05-15 13:39 ` w15303746062
2026-05-15 14:05 ` [PATCH v4] " w15303746062
2026-05-15 16:08 ` Luiz Augusto von Dentz
2026-05-16 1:41 ` w15303746062
2026-05-16 2:22 ` [PATCH v5] " w15303746062
2026-05-16 5:30 ` [PATCH v6] Bluetooth: hci_uart: fix UAFs and race conditions in close and init paths w15303746062
2026-05-16 8:47 ` [PATCH v7] " w15303746062
2026-05-18 1:36 ` [PATCH v8] " w15303746062
2026-05-18 2:49 ` [PATCH v9] " w15303746062
2026-05-19 15: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=177920280488.2756414.8251481561878776667.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=25181214217@stu.xidian.edu.cn \
--cc=greg@kroah.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pmenzel@molgen.mpg.de \
--cc=stable@vger.kernel.org \
--cc=w15303746062@163.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