All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Laxman Acharya Padhya <acharyalaxman8848@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
	marcel@holtmann.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: hci_codec: validate vendor codec count length
Date: Thu, 10 Sep 2026 19:50:05 +0000	[thread overview]
Message-ID: <178906980564.2055460.13921415718571070478.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260824155736.54542-1-acharyalaxman8848@gmail.com>

Hello:

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

On Mon, 24 Aug 2026 21:42:36 +0545 you wrote:
> The Read Local Supported Codecs parsers consume the variable-sized
> standard codec array before parsing the vendor codec count.  Although the
> initial reply-size check includes a vendor count byte in the fixed layout,
> it does not guarantee that the byte remains after the standard codec array.
> 
> If a controller reply ends immediately after that array, calculating the
> vendor codec array size reads vnd_codecs->num beyond the skb data.  Use
> skb_pull_data() to validate and consume each codec header before using its
> count in both command variants.
> 
> [...]

Here is the summary with links:
  - [v2] Bluetooth: hci_codec: validate vendor codec count length
    https://git.kernel.org/bluetooth/bluetooth-next/c/803d146cd56b

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-09-10 19:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23 16:16 [PATCH] Bluetooth: hci_codec: validate vendor codec count length Laxman Acharya Padhya
2026-08-23 17:18 ` bluez.test.bot
2026-08-24 14:28 ` [PATCH] " Luiz Augusto von Dentz
2026-08-24 14:40   ` Laxman Acharya Padhya
2026-08-24 15:01     ` Luiz Augusto von Dentz
2026-08-24 15:20       ` Laxman Acharya Padhya
2026-08-24 15:31         ` Luiz Augusto von Dentz
2026-08-24 15:57           ` [PATCH v2] " Laxman Acharya Padhya
2026-08-24 16:54             ` [v2] " bluez.test.bot
2026-09-10 19:15             ` bluez.test.bot
2026-09-10 19:50             ` 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=178906980564.2055460.13921415718571070478.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=acharyalaxman8848@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=stable@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.