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>,
Masaki Ota <masaki.ota@jp.alps.com>,
Rahul Rameshbabu <sergeantsagara@protonmail.com>,
Johannes Roith <johannes@gnu-linux.rocks>,
"Daniel M . Lambea" <dmlambea@gmail.com>,
"Derek J . Clark" <derekjohn.clark@gmail.com>,
Zhouwang Huang <honjow311@gmail.com>,
David Barksdale <dbarksdale@uplogix.com>,
Don Prince <dhprince-devel@yahoo.co.uk>,
Clemens Ladisch <clemens@ladisch.de>,
Tristan Madani <tristan@talencesecurity.com>
Subject: [PATCH 0/8] HID: validate report size in raw_event callbacks
Date: Sun, 18 Oct 2026 21:37:45 +0000 [thread overview]
Message-ID: <20261018213754.1951187-1-tristmd@gmail.com> (raw)
From: Tristan Madani <tristan@talencesecurity.com>
Several HID drivers access report data at fixed offsets in their
raw_event callbacks without checking that the buffer is large enough.
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 size validation to eight drivers:
- pxrc, cougar, zydacron, mcp2200, prodikeys: simple minimum size
- alps: per-report-type validation (touchpad, stick, absolute)
- oxp: per-report-type struct size validation
- cp2112: size checks for transfer status and data read responses,
plus capping the read copy length to the available buffer
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 | 3 +++
drivers/hid/hid-pxrc.c | 3 +++
drivers/hid/hid-zydacron.c | 3 +++
8 files changed, 43 insertions(+)
--
2.47.3
next reply other threads:[~2026-10-18 21:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 21:37 Tristan Madani [this message]
2026-10-18 21:37 ` [PATCH 1/8] HID: pxrc: validate report size in raw_event callback Tristan Madani
2026-10-18 21:37 ` [PATCH 2/8] HID: alps: validate report size in raw_event callbacks Tristan Madani
2026-10-18 21:45 ` sashiko-bot
2026-10-18 21:37 ` [PATCH 3/8] HID: mcp2200: validate report size in raw_event callback Tristan Madani
2026-10-18 21:37 ` [PATCH 4/8] HID: cougar: " Tristan Madani
2026-10-18 21:37 ` [PATCH 5/8] HID: zydacron: " Tristan Madani
2026-10-18 21:37 ` [PATCH 6/8] HID: oxp: validate report size in raw_event callbacks Tristan Madani
2026-10-18 21:48 ` sashiko-bot
2026-10-18 21:37 ` [PATCH 7/8] HID: cp2112: validate report size in raw_event callback Tristan Madani
2026-10-18 21:37 ` [PATCH 8/8] HID: prodikeys: " Tristan Madani
2026-10-18 21:44 ` sashiko-bot
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=20261018213754.1951187-1-tristmd@gmail.com \
--to=tristmd@gmail.com \
--cc=bentiss@kernel.org \
--cc=clemens@ladisch.de \
--cc=dbarksdale@uplogix.com \
--cc=derekjohn.clark@gmail.com \
--cc=dhprince-devel@yahoo.co.uk \
--cc=dmlambea@gmail.com \
--cc=honjow311@gmail.com \
--cc=jikos@kernel.org \
--cc=johannes@gnu-linux.rocks \
--cc=linux-input@vger.kernel.org \
--cc=marcus.folkesson@gmail.com \
--cc=masaki.ota@jp.alps.com \
--cc=sergeantsagara@protonmail.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.