From: Tristan Madani <tristmd@gmail.com>
To: Jiri Kosina <jikos@kernel.org>, Benjamin Tissoires <bentiss@kernel.org>
Cc: linux-input@vger.kernel.org,
Marcus Folkesson <marcus.folkesson@gmail.com>,
"Derek J . Clark" <derekjohn.clark@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Tristan Madani <tristan@talencesecurity.com>
Subject: [PATCH v2 0/8] HID: validate report size in raw_event callbacks
Date: Sun, 18 Oct 2026 22:03:36 +0000 [thread overview]
Message-ID: <20261018220344.1987142-1-tristmd@gmail.com> (raw)
From: Tristan Madani <tristan@talencesecurity.com>
Several HID drivers access report data in their raw_event callbacks
without first verifying the buffer length. Since hid-core invokes each
driver's raw_event callback before it validates the report length in
hid_report_raw_event(), these drivers must perform their own bounds
checking to handle short reports safely.
This series adds report size validation to eight drivers whose
raw_event handlers read beyond the first byte before any length check.
Tristan Madani (8):
HID: pxrc: validate report size in raw_event callback
HID: alps: validate report size in raw_event callbacks
HID: mcp2200: validate report size in raw_event callback
HID: cougar: validate report size in raw_event callback
HID: zydacron: validate report size in raw_event callback
HID: oxp: validate report size in raw_event callbacks
HID: cp2112: validate report size in raw_event callback
HID: prodikeys: validate report size in raw_event callback
drivers/hid/hid-alps.c | 12 ++++++++++++
drivers/hid/hid-cougar.c | 3 +++
drivers/hid/hid-cp2112.c | 10 ++++++++++
drivers/hid/hid-mcp2200.c | 3 +++
drivers/hid/hid-oxp.c | 6 ++++++
drivers/hid/hid-prodikeys.c | 4 ++++
drivers/hid/hid-pxrc.c | 3 +++
drivers/hid/hid-zydacron.c | 3 +++
8 files changed, 44 insertions(+)
---
Changes v1 -> v2:
- Patch 2/8 (alps): Fixed U1_ABSOLUTE report bound from
max_fingers * 5 + 5 to max_fingers * 5 + 3. The last byte accessed
in the finger loop is contact[7] at data[max_fingers * 5 + 2],
so the previous bound was two bytes too strict (reported by sashiko-bot).
- Patch 8/8 (prodikeys): Moved size checks into pcmidi_handle_report()
with per-report-ID guards instead of a blanket size < 4 in
pk_raw_event(). Report 0x03 (MIDI keyboard) passes size to
pcmidi_handle_report3() which already handles variable-length
reports; the blanket check dropped valid 3-byte single-note events
(reported by sashiko-bot).
--
2.47.3
next reply other threads:[~2026-10-18 22:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 22:03 Tristan Madani [this message]
2026-10-18 22:03 ` [PATCH v2 1/8] HID: pxrc: validate report size in raw_event callback Tristan Madani
2026-10-18 22:03 ` [PATCH v2 2/8] HID: alps: validate report size in raw_event callbacks Tristan Madani
2026-10-18 22:03 ` [PATCH v2 3/8] HID: mcp2200: validate report size in raw_event callback Tristan Madani
2026-10-18 22:03 ` [PATCH v2 4/8] HID: cougar: " Tristan Madani
2026-10-18 22:03 ` [PATCH v2 5/8] HID: zydacron: " Tristan Madani
2026-10-18 22:03 ` [PATCH v2 6/8] HID: oxp: validate report size in raw_event callbacks Tristan Madani
2026-10-18 22:13 ` sashiko-bot
2026-10-18 22:03 ` [PATCH v2 7/8] HID: cp2112: validate report size in raw_event callback Tristan Madani
2026-10-18 22:03 ` [PATCH v2 8/8] HID: prodikeys: " 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=20261018220344.1987142-1-tristmd@gmail.com \
--to=tristmd@gmail.com \
--cc=bentiss@kernel.org \
--cc=derekjohn.clark@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=marcus.folkesson@gmail.com \
--cc=tristan@talencesecurity.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.