Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] bap: Fix stack buffer overflow in BlueZ LE Audio BASE parser
Date: Thu, 27 Aug 2026 17:10:06 +0000	[thread overview]
Message-ID: <178785060639.1754949.17611133756001684186.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260827145807.1568199-1-hadess@hadess.net>

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Thu, 27 Aug 2026 16:58:00 +0200 you wrote:
> 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
> 
> [...]

Here is the summary with links:
  - bap: Fix stack buffer overflow in BlueZ LE Audio BASE parser
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=627f9fae7895

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-08-27 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27 14:58 [PATCH] bap: Fix stack buffer overflow in BlueZ LE Audio BASE parser Bastien Nocera
2026-08-27 16:17 ` bluez.test.bot
2026-08-27 17:10 ` patchwork-bot+bluetooth [this message]

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=178785060639.1754949.17611133756001684186.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=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