public inbox for linux-bluetooth@vger.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 BlueZ] shared/bap: fix crash when removing PAC
Date: Tue, 22 Apr 2025 09:11:15 +0000	[thread overview]
Message-ID: <174531307548.1477965.13329027277685740052.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <86080a21f6604cb916b89aba57a43afe57475a59.1745252940.git.pav@iki.fi>

Hello:

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

On Mon, 21 Apr 2025 19:30:54 +0300 you wrote:
> When PAC is removed, streams need to go through RELEASING flow, which in
> some cases is not immediate. Access to stream->lpac is UAF during this
> time, e.g. in profiles/audio/bap.c:bap_find_setup_by_stream
> 
> Allow stream->lpac == NULL. This should occur only if stream is
> RELEASING.
> 
> [...]

Here is the summary with links:
  - [BlueZ] shared/bap: fix crash when removing PAC
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=578a6fd688b0

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



  reply	other threads:[~2025-04-22  9:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-21 16:30 [PATCH BlueZ] bap: don't track streams without setup except for ucast server Pauli Virtanen
2025-04-21 16:30 ` [PATCH BlueZ] shared/bap: fix crash when removing PAC Pauli Virtanen
2025-04-22  9:11   ` patchwork-bot+bluetooth [this message]
2025-04-22  9:11 ` [PATCH BlueZ] bap: don't track streams without setup except for ucast server 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=174531307548.1477965.13329027277685740052.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