From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 5797a6: bass: Fix crashing on BT_BASS_MOD_SRC
Date: Tue, 14 Apr 2026 09:43:01 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/1ab128-d6171b@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 5797a61809ae0a214389b12c99b614ddd522f38e
https://github.com/bluez/bluez/commit/5797a61809ae0a214389b12c99b614ddd522f38e
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-14 (Tue, 14 Apr 2026)
Changed paths:
M profiles/audio/bass.c
Log Message:
-----------
bass: Fix crashing on BT_BASS_MOD_SRC
If assistant attempt o modify source the code would attempt to iterate
over all valid range of BIS indexes which may lead to the following
trace since the delegator maybe freed in the process:
#0 queue_find (queue=<optimized out>, function=function@entry=0x58b8761109c0 <setup_match_bis>, match_data=match_data@entry=0x3) at src/shared/queue.c:230
#1 0x000058b8761127fb in bass_update_bis_sync (bcast_src=<optimized out>, dg=<optimized out>) at profiles/audio/bass.c:1824
#2 handle_mod_src_req (data=<optimized out>, params=<optimized out>, bcast_src=0x58b894661be0) at profiles/audio/bass.c:1862
#3 cp_handler (bcast_src=0x58b894661be0, op=<optimized out>, params=<optimized out>, user_data=<optimized out>) at profiles/audio/bass.c:1910
#4 0x000058b8761bc978 in bass_handle_mod_src_op (bass=<optimized out>, attrib=<optimized out>, opcode=<optimized out>, id=<optimized out>, iov=<optimized out>, att=<optimized out>)
at src/shared/bass.c:1069
To fix the code will now just interate at existing setups checking if
they match the BIS index then adding/removing the stream so it is no
longer possible to free the delegator before all setups are processed.
Commit: d6171b00a2ae342c2b8266b6ee3350133ec55f20
https://github.com/bluez/bluez/commit/d6171b00a2ae342c2b8266b6ee3350133ec55f20
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-14 (Tue, 14 Apr 2026)
Changed paths:
M .github/workflows/ci.yml
Log Message:
-----------
workflow/ci: Add checks:write permission and explicit reopened trigger
The CI action now creates individual GitHub Check Runs per test, which
requires 'checks: write' permission on the GITHUB_TOKEN. Also make the
pull_request trigger types explicit to include 'reopened', allowing CI
to be retriggered by closing and reopening a PR.
Compare: https://github.com/bluez/bluez/compare/1ab128f6d749...d6171b00a2ae
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-04-14 16:43 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/master/1ab128-d6171b@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