From: Pengpeng Hou <pengpeng@iscas.ac.cn>
To: Mika Westerberg <westeri@kernel.org>
Cc: Andreas Noever <andreas.noever@gmail.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rajmohan Mani <rajmohan.mani@intel.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Pengpeng Hou <pengpeng@iscas.ac.cn>
Subject: [PATCH v3 0/2] thunderbolt: validate DROM entry extents
Date: Thu, 13 Aug 2026 23:22:06 +0800 [thread overview]
Message-ID: <20260813152206.28059-1-pengpeng@iscas.ac.cn> (raw)
The generic DROM walker can read a two-byte entry header from a one-byte
tail and accepts an entry whose declared length is shorter than that
header. Separately, the USB4 product descriptor parser reads a complete
struct tb_drom_entry_desc without requiring that structure to be present.
Split those contracts into two patches. The descriptor check now uses
sizeof(*desc), as requested by Mika Westerberg, instead of spelling out
the fields manually.
Changes since v2:
https://lore.kernel.org/all/20260731141700.3-thunderbolt-v2-pengpeng@iscas.ac.cn/
- split the generic entry and USB4 descriptor checks
- validate the USB4 entry with sizeof(*desc)
- rebase and re-review against the current tree
The series was reviewed statically. I did not test it with malformed
device DROM data.
Pengpeng Hou (2):
thunderbolt: require complete DROM entry headers
thunderbolt: validate USB4 product descriptor entry size
drivers/thunderbolt/eeprom.c | 18 +++++++++++++++---
1 file changed, 15 insertions(+), 3 deletions(-)
base-commit: f5bbbfec59b4e2fb7520a91de3df8a6174325d6a
--
2.50.1 (Apple Git-155)
next reply other threads:[~2026-08-13 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 15:22 Pengpeng Hou [this message]
2026-08-13 15:23 ` [PATCH v3 1/2] thunderbolt: require complete DROM entry headers Pengpeng Hou
2026-08-13 15:25 ` [PATCH v3 2/2] thunderbolt: validate USB4 product descriptor entry size Pengpeng Hou
2026-08-31 6:52 ` [PATCH v3 0/2] thunderbolt: validate DROM entry extents Mika Westerberg
2026-08-31 9:26 ` Mika Westerberg
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=20260813152206.28059-1-pengpeng@iscas.ac.cn \
--to=pengpeng@iscas.ac.cn \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rajmohan.mani@intel.com \
--cc=westeri@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