From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 5a7a91: shared/mcp: fix crash on destroy after ATT gone
Date: Mon, 06 Apr 2026 07:01:59 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1077654/000000-6a643e@github.com> (raw)
Branch: refs/heads/1077654
Home: https://github.com/bluez/bluez
Commit: 5a7a91116c9d6b1d9cab858b9d198ac3ff2fe329
https://github.com/bluez/bluez/commit/5a7a91116c9d6b1d9cab858b9d198ac3ff2fe329
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-04-06 (Mon, 06 Apr 2026)
Changed paths:
M src/shared/mcp.c
Log Message:
-----------
shared/mcp: fix crash on destroy after ATT gone
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.
Commit: 6a643eb08d1ccb622f847683e739aa242f2ef359
https://github.com/bluez/bluez/commit/6a643eb08d1ccb622f847683e739aa242f2ef359
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-04-06 (Mon, 06 Apr 2026)
Changed paths:
M src/shared/mcp.c
M unit/test-mcp.c
Log Message:
-----------
shared/mcp: fix parsing of control point arguments
Fix parsing of control point argument lost in rebases.
Add tests for Move Relative command that need it:
MCS/SR/MCP/BV-12-C [Move Relative from Playing]
MCS/SR/MCP/BV-13-C [Move Relative from Paused]
MCS/SR/MCP/BV-14-C [Move Relative from Seeking]
MCS/SR/MCP/BV-75-C [Move Relative from Inactive]
Compare: https://github.com/bluez/bluez/compare/5a7a91116c9d%5E...6a643eb08d1c
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-04-06 14:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1077654/000000-6a643e@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox