From: Bhavani <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 73ccf6: all: Fix typo in AVRCP_ATTRIBUTE_ILEGAL
Date: Thu, 27 Aug 2026 17:28:24 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/9f5adb-49592c@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 73ccf6d83e6a1c65bd4971c6e35da16520f7d74e
https://github.com/bluez/bluez/commit/73ccf6d83e6a1c65bd4971c6e35da16520f7d74e
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-08-27 (Thu, 27 Aug 2026)
Changed paths:
M monitor/avctp.c
M profiles/audio/avrcp.c
M profiles/audio/avrcp.h
M tools/parser/avrcp.c
M unit/avrcp-lib.c
M unit/avrcp-lib.h
Log Message:
-----------
all: Fix typo in AVRCP_ATTRIBUTE_ILEGAL
It's "illegal" not "ilegal".
Commit: 627f9fae78959cb38d5e48a7cc3f008ad746f39c
https://github.com/bluez/bluez/commit/627f9fae78959cb38d5e48a7cc3f008ad746f39c
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-08-27 (Thu, 27 Aug 2026)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
bap: Fix stack buffer overflow in BlueZ LE Audio BASE parser
A stack buffer overflow (CWE-121) in bap_sink_match_allocation() in
src/shared/bap.c allows an attacker within BLE range to write ~195
attacker-controlled bytes past a 4-byte stack buffer in bluetoothd
with no pairing, no connection, and no user interaction. The BAP
profile auto-syncs to any device advertising the BCAAS UUID.
bap_sink_match_allocation() copies the value of an
Audio_Channel_Allocation LTV (type 0x03) into a 4-byte uint32_t stack
local using the LTV's attacker-controlled length byte as the memcpy
size, with no upper bound check:
// src/shared/bap.c:7767
memcpy(&location32, v, l); // l attacker-controlled, no upper bound
A second identical instance exists in bap_sink_get_allocation() at line 2558.
Per Bluetooth Assigned Numbers, Audio_Channel_Allocation is a fixed 4-octet
bitfield; any other length is malformed.
https://github.com/bluez/bluez/security/advisories/GHSA-9683-2chf-hfw9
Co-Authored-by: @thaidn and @bronson-calif of Calif.io in collaboration with
Claude and Anthropic Research.
Reported-by: @thaidn and @bronson-calif of Calif.io in collaboration with
Claude and Anthropic Research.
Reported-by: @thaidn and @bronson-calif of Calif.io in collaboration with
Commit: 3c18444ced8e40067a855560d6fc18cda21efaba
https://github.com/bluez/bluez/commit/3c18444ced8e40067a855560d6fc18cda21efaba
Author: Bastien Nocera <hadess@hadess.net>
Date: 2026-08-27 (Thu, 27 Aug 2026)
Changed paths:
M src/shared/bass.c
Log Message:
-----------
bass: Fix heap buffer overflow allocating subgroup_data array
bass_build_bcast_src() in src/shared/bass.c parses the Broadcast Receive State
characteristic value received from a remote BASS server.
It reads an attacker-controlled num_subgroups byte (range 0-255) but always
allocates a single bt_bass_subgroup_data entry (24 bytes):
subgroup_data = new0(struct bt_bass_subgroup_data, 1); // line 337: always 1
for (int i = 0; i < num_subgroups; i++) { // line 343: up to 255
subgroup_data[i].bis_sync = bis_sync_state; // line 355: OOB write
Reported-by: @thaidn and @bronson-calif of Calif.io in collaboration
with Claude and Anthropic Research
Suggested-by: @trace37labs for the Fixes
Fixes: 8980f4f1f7 ("shared/bass: Functions cleanup")
See: https://github.com/bluez/bluez/security/advisories/GHSA-7wjj-8mrm-jhw4
Reported-by: @thaidn and @bronson-calif of Calif.io in collaboration
Commit: d094be10ff0cc9d48714d35557e0fd297f36f907
https://github.com/bluez/bluez/commit/d094be10ff0cc9d48714d35557e0fd297f36f907
Author: Jinwang Li <jinwang.li@oss.qualcomm.com>
Date: 2026-08-27 (Thu, 27 Aug 2026)
Changed paths:
M gobex/gobex-transfer.c
Log Message:
-----------
gobex: Fix ABORT response being discarded
g_obex_drop_tx_queue() in transfer_complete() clears any pending tx,
so the ABORT success response should be enqueued after transfer_complete().
Fixes the following PTS test cases:
- OPP/SR/OPH/BV-27-I
- FTP/SR/OTR/BV-02-C
- PBAP/PSE/PDF/BV-06-I
- PBAP/PSE/PBF/BV-03-I
Fixes: 7a35c12a6ceb ("gobex: Fix segfault caused by interrupted transfer")
Assisted-by: Claude:claude-sonnet-5
Commit: 06b1ba3343c56ed71e9a45aa0439ebbaec9c0072
https://github.com/bluez/bluez/commit/06b1ba3343c56ed71e9a45aa0439ebbaec9c0072
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-08-27 (Thu, 27 Aug 2026)
Changed paths:
M src/main.conf
Log Message:
-----------
src: Modify MaxTxPower option documentation for ChannelSounding
Modify MaxTxPower configuration option to take decimal values
within the range of -127dBm to 20dBm
Defaults to 20 (max power).
Commit: 49592cbc141675d15d13c83ea190ae438684bb09
https://github.com/bluez/bluez/commit/49592cbc141675d15d13c83ea190ae438684bb09
Author: Naga Bhavani Akella <naga.akella@oss.qualcomm.com>
Date: 2026-08-27 (Thu, 27 Aug 2026)
Changed paths:
M client/cs.c
Log Message:
-----------
client: Enforce Valid Main Mode and Sub Mode Combinations
Introduce validation for main_mode_type and sub_mode_type combinations as
specified in the protocol requirements.
Reject invalid combinations and guide the user by displaying
the acceptable mode pairings.
Compare: https://github.com/bluez/bluez/compare/9f5adb00c7c1...49592cbc1416
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-08-28 0:28 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/9f5adb-49592c@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