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,
	iulia.tanasescu@nxp.com, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: ISO: Reject concurrent BIS listener setup
Date: Tue, 06 Oct 2026 14:30:15 +0000	[thread overview]
Message-ID: <179129701552.2655967.7619580785559847090.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261004162548.3968712-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:25:48 +0800 you wrote:
> iso_sock_listen() drops the socket lock before calling iso_listen_bis()
> to preserve the hdev->lock ordering. Two concurrent listen() calls on
> the same broadcast socket can therefore both observe BT_BOUND. Caller
> A can attach connA and release the locks, then caller B can acquire
> them and attach connB before A publishes BT_LISTEN.
> 
> __iso_chan_add() checks whether connB already has a socket, but not
> whether the socket already has a connection. The second attachment
> overwrites iso_pi(sk)->conn, leaking the connA reference and leaving
> connA->sk intact. Socket teardown follows connB, so later events on
> connA can cause a stale socket access.
> 
> [...]

Here is the summary with links:
  - Bluetooth: ISO: Reject concurrent BIS listener setup
    https://git.kernel.org/bluetooth/bluetooth-next/c/555ff78fa719

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:25 [PATCH] Bluetooth: ISO: Reject concurrent BIS listener setup Chengfeng Ye
2026-10-04 18:54 ` 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=179129701552.2655967.7619580785559847090.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=iulia.tanasescu@nxp.com \
    --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=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.