All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Chengfeng Ye <nicoyip.dev@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	penguin-kernel@i-love.sakura.ne.jp,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_sock: Serialize dead-device detachment
Date: Tue, 06 Oct 2026 14:30:12 +0000	[thread overview]
Message-ID: <179129701278.2655967.8493236646880910714.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261004162442.3968446-1-nicoyip.dev@gmail.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Mon,  5 Oct 2026 00:24:42 +0800 you wrote:
> Rebinding an HCI socket after its controller is unregistered can race
> monitor control replay and crash the kernel. hci_sock_bind() clears
> hci_pi(sk)->hdev and drops the device reference under only the socket
> lock, whereas send_monitor_control_replay() holds hci_sk_list.lock for
> reading.
> 
> Replay can observe a non-NULL hdev, then bind can clear it and drop the
> last reference before create_monitor_ctrl_open() reads hdev->id. This
> can cause a NULL pointer dereference if the pointer is reloaded, or a
> use-after-free if the old pointer is retained.
> 
> [...]

Here is the summary with links:
  - Bluetooth: hci_sock: Serialize dead-device detachment
    https://git.kernel.org/bluetooth/bluetooth-next/c/381a0925c556

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-06 14:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04 16:24 [PATCH] Bluetooth: hci_sock: Serialize dead-device detachment Chengfeng Ye
2026-10-04 18:49 ` bluez.test.bot
2026-10-06 14:30 ` 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=179129701278.2655967.8493236646880910714.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=nicoyip.dev@gmail.com \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=stable@vger.kernel.org \
    /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.