From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/2] shared/mcp: fix crash on destroy after ATT gone
Date: Mon, 06 Apr 2026 17:00:13 +0000 [thread overview]
Message-ID: <177549481353.3188653.15823430730825612852.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <020cbb8375aacc6d8d9edad9aca96a6cde131dfb.1775481285.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 6 Apr 2026 16:15:19 +0300 you wrote:
> Tie lifetime of bt_mcs_session to that of ATT disconnect watch. The
> disconnect handler is not necessarily called before ATT is freed, but
> destroy is.
>
> Fixes UAF of session->att in bt_mcs_unregister() -> session_destroy() ->
> bt_att_unregister_disconnect() if ATT was freed first.
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/2] shared/mcp: fix crash on destroy after ATT gone
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=46b859d82909
- [BlueZ,v2,2/2] shared/mcp: fix parsing of control point arguments
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=21db57fc0c2f
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-04-06 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 13:15 [PATCH BlueZ v2 1/2] shared/mcp: fix crash on destroy after ATT gone Pauli Virtanen
2026-04-06 13:15 ` [PATCH BlueZ v2 2/2] shared/mcp: fix parsing of control point arguments Pauli Virtanen
2026-04-06 14:50 ` [BlueZ,v2,1/2] shared/mcp: fix crash on destroy after ATT gone bluez.test.bot
2026-04-06 17: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=177549481353.3188653.15823430730825612852.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