From: Bastien Nocera <hadess@hadess.net>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH] bap: Fix stack buffer overflow in BlueZ LE Audio BASE parser
Date: Thu, 27 Aug 2026 16:58:00 +0200 [thread overview]
Message-ID: <20260827145807.1568199-1-hadess@hadess.net> (raw)
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.
---
src/shared/bap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/shared/bap.c b/src/shared/bap.c
index 1660b8b2c1cf..da3e265e2077 100644
--- a/src/shared/bap.c
+++ b/src/shared/bap.c
@@ -2555,7 +2555,7 @@ static void bap_sink_get_allocation(size_t i, uint8_t l, uint8_t t,
{
uint32_t location32;
- if (!v)
+ if (!v || l != sizeof(location32))
return;
memcpy(&location32, v, l);
@@ -7764,7 +7764,7 @@ static void bap_sink_match_allocation(size_t i, uint8_t l, uint8_t t,
struct bt_ltv_match *data = user_data;
uint32_t location32;
- if (!v)
+ if (!v || l != sizeof(location32))
return;
memcpy(&location32, v, l);
--
2.55.0
next reply other threads:[~2026-08-27 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 14:58 Bastien Nocera [this message]
2026-08-27 16:17 ` bap: Fix stack buffer overflow in BlueZ LE Audio BASE parser bluez.test.bot
2026-08-27 17:10 ` [PATCH] " patchwork-bot+bluetooth
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=20260827145807.1568199-1-hadess@hadess.net \
--to=hadess@hadess.net \
--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