From: patchwork-bot+bluetooth@kernel.org
To: Catherine L <catherine.l@intel.com>
Cc: linux-bluetooth@vger.kernel.org, kiran.k@intel.com,
chethan.tumkur.narayan@intel.com
Subject: Re: [PATCH v1] Bluetooth: btintel: fix buffer over-read in fw payload
Date: Fri, 23 Oct 2026 21:00:36 +0000 [thread overview]
Message-ID: <179278923631.1268720.7892798923940223357.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261023060026.524147-1-catherine.l@intel.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 23 Oct 2026 11:30:26 +0530 you wrote:
> The firmware decoder cast fw_ptr + frag_len to struct
> hci_command_hdr and read cmd->plen before confirming the
> header and payload still fit in the remaining firmware
> buffer.
>
> Add explicit bounds checks before each dereference:
> 1. Reject if the command header is not fully contained
> in remain.
> 2. Reject if the full command including payload exceeds
> remain.
> 3. Log the offending fragment length and remaining size
> before returning -EINVAL.
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: btintel: fix buffer over-read in fw payload
https://git.kernel.org/bluetooth/bluetooth-next/c/4891a9f76d0f
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-10-23 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 6:00 [PATCH v1] Bluetooth: btintel: fix buffer over-read in fw payload Catherine L
2026-10-23 7:31 ` [v1] " bluez.test.bot
2026-10-23 21:00 ` 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=179278923631.1268720.7892798923940223357.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=catherine.l@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox