From: patchwork-bot+bluetooth@kernel.org
To: Kiran K <kiran.k@intel.com>
Cc: linux-bluetooth@vger.kernel.org,
chethan.tumkur.narayan@intel.com,
chandrashekar.devegowda@intel.com
Subject: Re: [PATCH v4 1/2] Bluetooth: btintel: Zero version data before parsing TLVs
Date: Fri, 09 Oct 2026 19:50:05 +0000 [thread overview]
Message-ID: <179157540571.979491.7048149964326431480.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261008140602.2623464-1-kiran.k@intel.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 8 Oct 2026 19:36:01 +0530 you wrote:
> Firmware may omit optional TLVs, leaving their corresponding fields
> unset in the caller-supplied struct intel_version_tlv. Since the
> structure is typically stack-allocated and not cleared beforehand,
> fields for which no TLV is received retain uninitialized stack
> memory. This stale data can be logged via btintel_version_info_tlv()
> and copied back to the caller, leaking kernel stack contents.
>
> [...]
Here is the summary with links:
- [v4,1/2] Bluetooth: btintel: Zero version data before parsing TLVs
https://git.kernel.org/bluetooth/bluetooth-next/c/21c8238e1b1d
- [v4,2/2] Bluetooth: btintel: load unlocker.sfi to allow unsigned firmware
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-10-09 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 14:06 [PATCH v4 1/2] Bluetooth: btintel: Zero version data before parsing TLVs Kiran K
2026-10-08 14:06 ` [PATCH v4 2/2] Bluetooth: btintel: load unlocker.sfi to allow unsigned firmware Kiran K
2026-10-08 15:26 ` [v4,1/2] Bluetooth: btintel: Zero version data before parsing TLVs bluez.test.bot
2026-10-09 14:00 ` Luiz Augusto von Dentz
2026-10-09 19:50 ` patchwork-bot+bluetooth [this message]
2026-10-09 20:00 ` [PATCH v4 1/2] " patchwork-bot+bluetooth
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=179157540571.979491.7048149964326431480.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chandrashekar.devegowda@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