All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER
Date: Tue, 31 Mar 2026 14:30:09 +0000	[thread overview]
Message-ID: <177496740953.2731558.12495255644281555301.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <089f435fb4668921bb416a3d60fa0f232456e054.1774791296.git.pav@iki.fi>

Hello:

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

On Sun, 29 Mar 2026 16:42:59 +0300 you wrote:
> When protocol sets HCI_PROTO_DEFER, hci_conn_request_evt() calls
> hci_connect_cfm(conn) without hdev->lock. Generally hci_connect_cfm()
> assumes it is held, and if conn is deleted concurrently -> UAF.
> 
> Only SCO and ISO set HCI_PROTO_DEFER and only for defer setup listen,
> and HCI_EV_CONN_REQUEST is not generated for ISO.  In the non-deferred
> listening socket code paths, hci_connect_cfm(conn) is called with
> hdev->lock held.
> 
> [...]

Here is the summary with links:
  - Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER
    https://git.kernel.org/bluetooth/bluetooth-next/c/31798ffc35a9

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-03-31 14:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-29 13:42 [PATCH] Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER Pauli Virtanen
2026-03-29 13:43 ` [PATCH] Bluetooth: hci_sync: fix refcounting in le_read_features_complete Pauli Virtanen
2026-03-29 14:11   ` bluez.test.bot
2026-03-30 13:32   ` [PATCH] " Luiz Augusto von Dentz
2026-03-29 13:43 ` [PATCH v3] Bluetooth: hci_conn: fix potential UAF in set_cig_params_sync Pauli Virtanen
2026-03-29 14:10   ` [v3] " bluez.test.bot
2026-03-31 14:30   ` [PATCH v3] " patchwork-bot+bluetooth
2026-03-29 13:43 ` [PATCH v3] Bluetooth: hci_event: fix potential UAF in hci_le_remote_conn_param_req_evt Pauli Virtanen
2026-03-29 14:11   ` [v3] " bluez.test.bot
2026-03-31 14:30   ` [PATCH v3] " patchwork-bot+bluetooth
2026-03-29 14:10 ` Bluetooth: fix locking in hci_conn_request_evt() with HCI_PROTO_DEFER bluez.test.bot
2026-03-31 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=177496740953.2731558.12495255644281555301.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pav@iki.fi \
    /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.