From: patchwork-bot+bluetooth@kernel.org
To: Ren Wei <n05ec@lzu.edu.cn>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, kiran.k@intel.com,
chethan.tumkur.narayan@intel.com, ravishankar.srivatsa@intel.com,
yuantan098@gmail.com, zcliangcn@gmail.com, bird@lzu.edu.cn,
xuyq21@lenovo.com
Subject: Re: [PATCH 1/1] Bluetooth: hci_codec: validate capability record length
Date: Wed, 10 Jun 2026 15:40:15 +0000 [thread overview]
Message-ID: <178110601591.3101197.7289209154305799030.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <4927cae4fe043f3e2aa80f4ee6bed05e4fb5a6d4.1779633761.git.xuyq21@lenovo.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 29 May 2026 21:12:25 +0800 you wrote:
> From: Yuqi Xu <xuyq21@lenovo.com>
>
> hci_read_codec_capabilities() validates each capability entry before
> adding its serialized size to len and advancing the skb.
>
> The current check only compares skb->len against caps->len, even
> though the code consumes the length byte and the payload. Validate
> the full record size so the cached capability length matches the
> bytes available in the command response.
>
> [...]
Here is the summary with links:
- [1/1] Bluetooth: hci_codec: validate capability record length
https://git.kernel.org/bluetooth/bluetooth-next/c/246dc2ed724b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-10 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1779633761.git.xuyq21@lenovo.com>
2026-05-29 13:12 ` [PATCH 1/1] Bluetooth: hci_codec: validate capability record length Ren Wei
2026-05-29 14:08 ` Luiz Augusto von Dentz
2026-05-29 15:09 ` [1/1] " bluez.test.bot
2026-06-10 15:40 ` 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=178110601591.3101197.7289209154305799030.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=bird@lzu.edu.cn \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=n05ec@lzu.edu.cn \
--cc=ravishankar.srivatsa@intel.com \
--cc=xuyq21@lenovo.com \
--cc=yuantan098@gmail.com \
--cc=zcliangcn@gmail.com \
/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