From: patchwork-bot+bluetooth@kernel.org
To: Sarveshwar Bajaj <sarveshwar.bajaj@nxp.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
vinit.mehta@nxp.com, devyani.godbole@nxp.com
Subject: Re: [PATCH BlueZ v2 0/1] Fix use-after-free in BAP broadcast cleanup
Date: Tue, 17 Feb 2026 14:50:06 +0000 [thread overview]
Message-ID: <177133980631.109268.5480162574757779566.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260214153616.655-1-sarveshwar.bajaj@nxp.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 14 Feb 2026 21:06:14 +0530 you wrote:
> This fixes a use-after-free crash when broadcast audio sources
> disconnect or undergo RPA rotation as reported in issue #1866.
>
> The crash occurs because bap_data_free() was freeing streams before
> destroying the broadcast sink setups that still held references to them.
>
> Tested with AddressSanitizer on latest 6.19 kernel with NXPs
> controller as broadcast sink and Samsung S23 broadcast source.
> No crashes observed with disconnect or RPA rotation after fix.
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/1] bap: Fix use-after-free in broadcast sink cleanup
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=feb4ee9dcd4b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-02-17 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 15:36 [PATCH BlueZ v2 0/1] Fix use-after-free in BAP broadcast cleanup Sarveshwar Bajaj
2026-02-14 15:36 ` [PATCH BlueZ v2 1/1] bap: Fix use-after-free in broadcast sink cleanup Sarveshwar Bajaj
2026-02-14 16:34 ` Fix use-after-free in BAP broadcast cleanup bluez.test.bot
2026-02-17 14:50 ` 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=177133980631.109268.5480162574757779566.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=devyani.godbole@nxp.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=sarveshwar.bajaj@nxp.com \
--cc=vinit.mehta@nxp.com \
/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