From: patchwork-bot+bluetooth@kernel.org
To: Rong Zhang <i@rong.moe>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
alex_lu@realsil.com.cn, max.chou@realtek.com,
allen_chen@realsil.com.cn, luiz.von.dentz@intel.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btrtl: Don't leak return code when parsing firmware format v2
Date: Thu, 03 Sep 2026 20:00:18 +0000 [thread overview]
Message-ID: <178846561855.3994681.6237344995216592209.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260903-btrtl-fix-patch-sec-header-rc-leak-v1-1-0ce37e2149bd@rong.moe>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 03 Sep 2026 03:18:59 +0800 you wrote:
> When key_id from chip is zero, rtlbt_parse_firmware_v2() intentionally
> ignores all security headers. However, the implementation simply breaks
> from a switch statement and leaks uninitialized return code `rc' (if the
> first section is a security one) or the previous section's `rc'.
>
> Fix it by really skipping a loop with `continue'. For consistency and
> readability, also do the same for the default case.
>
> [...]
Here is the summary with links:
- Bluetooth: btrtl: Don't leak return code when parsing firmware format v2
https://git.kernel.org/bluetooth/bluetooth-next/c/0aab041d532f
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-09-03 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 19:18 [PATCH] Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 Rong Zhang
2026-09-02 21:58 ` bluez.test.bot
2026-09-03 20: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=178846561855.3994681.6237344995216592209.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=alex_lu@realsil.com.cn \
--cc=allen_chen@realsil.com.cn \
--cc=i@rong.moe \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=max.chou@realtek.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox