From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v3] Bluetooth: hci_conn: fix potential UAF in set_cig_params_sync
Date: Tue, 31 Mar 2026 14:30:05 +0000 [thread overview]
Message-ID: <177496740554.2731558.2506628875970689257.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <5d61842fafed29f489f472bc6cb324e41f568083.1774787573.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:43:01 +0300 you wrote:
> hci_conn lookup and field access must be covered by hdev lock in
> set_cig_params_sync, otherwise it's possible it is freed concurrently.
>
> Take hdev lock to prevent hci_conn from being deleted or modified
> concurrently. Just RCU lock is not suitable here, as we also want to
> avoid "tearing" in the configuration.
>
> [...]
Here is the summary with links:
- [v3] Bluetooth: hci_conn: fix potential UAF in set_cig_params_sync
https://git.kernel.org/bluetooth/bluetooth-next/c/e00e94a42852
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev 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 ` patchwork-bot+bluetooth [this message]
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 ` [PATCH] " patchwork-bot+bluetooth
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=177496740554.2731558.2506628875970689257.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox