From: patchwork-bot+bluetooth@kernel.org
To: Laxman Acharya Padhya <acharyalaxman8848@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, linux-kernel@vger.kernel.org,
ali@iusegentoo.com, kiraank@gmail.com, kiran.k@intel.com,
ravishankar.srivatsa@intel.com, amit.k.bag@intel.com
Subject: Re: [PATCH v3 0/3] Bluetooth: btintel: harden version TLV parsing
Date: Mon, 31 Aug 2026 17:20:13 +0000 [thread overview]
Message-ID: <178819681363.671757.16024867125795377604.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260831095923.18830-1-acharyalaxman8848@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 31 Aug 2026 15:44:20 +0545 you wrote:
> Malformed Intel version TLVs can make btintel_parse_version_tlv() read
> beyond the received response. Validate the minimum value length for each
> known fixed-size TLV and bound the firmware ID conversion by the TLV's
> advertised length. Propagate parser failures to the setup path in a
> separate patch.
>
> The two bounds fixes are kept separate because they were introduced by
> different commits and apply to different stable trees. The parser error
> propagation is also separate because it changes setup behavior.
>
> [...]
Here is the summary with links:
- [v3,1/3] Bluetooth: btintel: validate version TLV value lengths
https://git.kernel.org/bluetooth/bluetooth-next/c/eb656c5bb754
- [v3,2/3] Bluetooth: btintel: bound firmware ID by TLV length
https://git.kernel.org/bluetooth/bluetooth-next/c/58c6f5ec1d22
- [v3,3/3] Bluetooth: btintel: propagate version TLV parsing errors
https://git.kernel.org/bluetooth/bluetooth-next/c/f8c8fa407aa0
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-08-31 17:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 17:15 [PATCH v2 0/3] Bluetooth: btintel: harden version TLV parsing Laxman Acharya Padhya
2026-08-14 17:15 ` [PATCH v2 1/3] Bluetooth: btintel: validate version TLV value lengths Laxman Acharya Padhya
2026-08-14 18:29 ` Bluetooth: btintel: harden version TLV parsing bluez.test.bot
2026-08-14 17:15 ` [PATCH v2 2/3] Bluetooth: btintel: bound firmware ID by TLV length Laxman Acharya Padhya
2026-08-14 17:15 ` [PATCH v2 3/3] Bluetooth: btintel: propagate version TLV parsing errors Laxman Acharya Padhya
2026-08-14 18:46 ` Ali Ahmet Memis
2026-08-31 9:59 ` [PATCH v3 0/3] Bluetooth: btintel: harden version TLV parsing Laxman Acharya Padhya
2026-08-31 9:59 ` [PATCH v3 1/3] Bluetooth: btintel: validate version TLV value lengths Laxman Acharya Padhya
2026-08-31 11:05 ` K, Kiran
2026-08-31 12:29 ` Bluetooth: btintel: harden version TLV parsing bluez.test.bot
2026-08-31 9:59 ` [PATCH v3 2/3] Bluetooth: btintel: bound firmware ID by TLV length Laxman Acharya Padhya
2026-08-31 11:05 ` K, Kiran
2026-08-31 9:59 ` [PATCH v3 3/3] Bluetooth: btintel: propagate version TLV parsing errors Laxman Acharya Padhya
2026-08-31 11:05 ` K, Kiran
2026-08-31 17:20 ` 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=178819681363.671757.16024867125795377604.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=acharyalaxman8848@gmail.com \
--cc=ali@iusegentoo.com \
--cc=amit.k.bag@intel.com \
--cc=kiraank@gmail.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=ravishankar.srivatsa@intel.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 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.