mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
	luiz.dentz@gmail.com, oss@fourdim.xyz,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/7] Bluetooth: hci_conn: hold conn reference in abort_conn_sync()
Date: Mon, 27 Jul 2026 19:00:08 +0000	[thread overview]
Message-ID: <178517880851.1372023.12829411898419783534.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <7a22e9136652bfc95b52bacc146e5ac461b82ec2.1782645211.git.pav@iki.fi>

Hello:

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

On Sun, 28 Jun 2026 15:12:32 +0300 you wrote:
> There is theoretical UAF if the conn is freed while the hci_sync task is
> running.
> 
> Hold refcount to avoid that.
> 
> Fixes: 227a0cdf4a02 ("Bluetooth: MGMT: Fix not generating command complete for MGMT_OP_DISCONNECT")
> Signed-off-by: Pauli Virtanen <pav@iki.fi>
> 
> [...]

Here is the summary with links:
  - [v3,1/7] Bluetooth: hci_conn: hold conn reference in abort_conn_sync()
    https://git.kernel.org/bluetooth/bluetooth-next/c/3bf1394e8868
  - [v3,2/7] Bluetooth: hci_sync: hold conn in hci_connect_acl/le_sync() callbacks
    https://git.kernel.org/bluetooth/bluetooth-next/c/69a694ebe97f
  - [v3,3/7] Bluetooth: hci_sync: hold conn in hci_connect_big_sync() callback
    (no matching commit)
  - [v3,4/7] Bluetooth: hci_sync: hold conn in hci_connect_pa_sync() callback
    https://git.kernel.org/bluetooth/bluetooth-next/c/cddfec3618d0
  - [v3,5/7] Bluetooth: hci_sync: hold conn in hci_past_sync() callback
    https://git.kernel.org/bluetooth/bluetooth-next/c/3c5f5c6be878
  - [v3,6/7] Bluetooth: hci_sync: fix hci_conn_del() use in hci_le_create_conn_sync
    https://git.kernel.org/bluetooth/bluetooth-next/c/423e5fc465eb
  - [v3,7/7] Bluetooth: hci_sync: remove unnecessary hci_conn_get in create_conn_sync
    https://git.kernel.org/bluetooth/bluetooth-next/c/73b6871b261f

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-07-27 19:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-28 12:12 Pauli Virtanen
2026-06-28 12:12 ` [PATCH v3 2/7] Bluetooth: hci_sync: hold conn in hci_connect_acl/le_sync() callbacks Pauli Virtanen
2026-06-28 12:12 ` [PATCH v3 3/7] Bluetooth: hci_sync: hold conn in hci_connect_big_sync() callback Pauli Virtanen
2026-06-28 12:12 ` [PATCH v3 4/7] Bluetooth: hci_sync: hold conn in hci_connect_pa_sync() callback Pauli Virtanen
2026-06-28 12:12 ` [PATCH v3 5/7] Bluetooth: hci_sync: hold conn in hci_past_sync() callback Pauli Virtanen
2026-06-28 12:12 ` [PATCH v3 6/7] Bluetooth: hci_sync: fix hci_conn_del() use in hci_le_create_conn_sync Pauli Virtanen
2026-06-28 12:12 ` [PATCH v3 7/7] Bluetooth: hci_sync: remove unnecessary hci_conn_get in create_conn_sync Pauli Virtanen
2026-07-27 19: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=178517880851.1372023.12829411898419783534.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=oss@fourdim.xyz \
    --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

all inboxes | Powered by JetHome®