From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] fe6513: bass: Fix possible crash on bass_update_bis_sync
Date: Tue, 23 Jun 2026 13:27:00 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1115551/000000-a0072e@github.com> (raw)
Branch: refs/heads/1115551
Home: https://github.com/bluez/bluez
Commit: fe6513bee8e6a73f926392b754020e62ade4cea0
https://github.com/bluez/bluez/commit/fe6513bee8e6a73f926392b754020e62ade4cea0
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-06-23 (Tue, 23 Jun 2026)
Changed paths:
M profiles/audio/bass.c
Log Message:
-----------
bass: Fix possible crash on bass_update_bis_sync
bass_update_bis_sync does use bass_remove_bis which may end up
removing the current entry causing a crash on entry->next, to avoid
that prefetch the next entry.
Commit: d94c2e27556c19c45a93feb9b6d50f01ba4b2ec0
https://github.com/bluez/bluez/commit/d94c2e27556c19c45a93feb9b6d50f01ba4b2ec0
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-06-23 (Tue, 23 Jun 2026)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Check if stream is valid before attempting to release
bt_bap_stream_release shall check if the stream is still valid before
attempting to release it just as done with other operations.
Commit: a0072e317879e12e6fe474950721384e84248d30
https://github.com/bluez/bluez/commit/a0072e317879e12e6fe474950721384e84248d30
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-06-23 (Tue, 23 Jun 2026)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: Don't transition to IDLE inside bap_bcast_set_state
Remove the recursive stream_set_state(IDLE) call from the RELEASING
case in bap_bcast_set_state. This call re-entered bap_bcast_set_state
while the state_cbs queue was still being iterated, causing a
use-after-free if a callback unregistered itself during notification.
Compare: https://github.com/bluez/bluez/compare/fe6513bee8e6%5E...a0072e317879
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-06-23 20:27 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/1115551/000000-a0072e@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