From: hadess <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] ce408c: bap: Fix stack buffer overflow in BlueZ LE Audio B...
Date: Thu, 27 Aug 2026 08:27:58 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1152690/000000-ce408c@github.com> (raw)
Branch: refs/heads/1152690
Home: https://github.com/bluez/bluez
Commit: ce408cacdb61d3137360268227f5c4aa31fce899
https://github.com/bluez/bluez/commit/ce408cacdb61d3137360268227f5c4aa31fce899
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.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-08-27 15: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/1152690/000000-ce408c@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.