From: Tristan Madani <tristmd@gmail.com>
To: Even Xu <even.xu@intel.com>, Xinpeng Sun <xinpeng.sun@intel.com>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@kernel.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Mark Pearson <mpearson-lenovo@squebb.ca>,
linux-input@vger.kernel.org, stable@vger.kernel.org,
Tristan Madani <tristan@talencesecurity.com>
Subject: [PATCH v3 0/2] HID: intel-thc-hid: validate ACPI buffer lengths
Date: Thu, 29 Oct 2026 14:10:34 +0000 [thread overview]
Message-ID: <20261029141037.2655603-1-tristmd@gmail.com> (raw)
From: Tristan Madani <tristan@talencesecurity.com>
The QuickSPI and QuickI2C ACPI helper functions copy firmware-returned
buffers without verifying their length. This series adds buf_size
parameters and overflow checks.
Changes in v3:
- Split into two separate patches (QuickSPI and QuickI2C), per Even Xu
- Add kernel-doc @buf_size parameter descriptions
Changes in v2:
- Use overflow-only check (>) instead of exact-match (!=)
- Zero-initialize caller stack structures
- Add missing type validation and kfree in DSD helper
Tristan Madani (2):
HID: intel-thc-hid: quickspi: validate ACPI buffer length before
memcpy
HID: intel-thc-hid: quicki2c: validate ACPI buffer length before
memcpy
.../intel-quicki2c/pci-quicki2c.c | 42 ++++++++++++++-----
.../intel-quickspi/pci-quickspi.c | 37 +++++++++-------
2 files changed, 54 insertions(+), 25 deletions(-)
--
2.47.3
next reply other threads:[~2026-10-29 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 14:10 Tristan Madani [this message]
2026-10-29 14:10 ` [PATCH v3 1/2] HID: intel-thc-hid: quickspi: validate ACPI buffer length before memcpy Tristan Madani
2026-10-29 14:10 ` [PATCH v3 2/2] HID: intel-thc-hid: quicki2c: " Tristan Madani
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=20261029141037.2655603-1-tristmd@gmail.com \
--to=tristmd@gmail.com \
--cc=bentiss@kernel.org \
--cc=even.xu@intel.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=tristan@talencesecurity.com \
--cc=xinpeng.sun@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox