From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: David Heidelberg <david@ixit.cz>, Andi Shyti <andi.shyti@kernel.org>
Cc: Petr Hodina <petr.hodina@protonmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/3] Input: stmfts - validate slot ID in touch events
Date: Tue, 3 Nov 2026 14:58:42 -0800 [thread overview]
Message-ID: <20261103225923.3892612-3-dmitry.torokhov@gmail.com> (raw)
In-Reply-To: <20261103225923.3892612-1-dmitry.torokhov@gmail.com>
Both FTS4 and FTS5 contact and release reporting functions extract a
4-bit slot/touch ID (values 0 to 15) from the event payload. However,
the driver initializes only STMFTS_MAX_FINGERS (10) multi-touch slots.
Passing a slot ID greater than or equal to STMFTS_MAX_FINGERS to
input_mt_slot() is silently rejected by the input core without updating
mt->slot, which causes subsequent slot state, coordinate, or release
reports to corrupt or release the previously active slot.
Validate that the slot ID is strictly less than STMFTS_MAX_FINGERS in
stmfts_report_contact_event(), stmfts_report_contact_release(),
stmfts5_report_contact_event(), and stmfts5_report_contact_release(),
logging a warning and returning early when an invalid slot ID is
encountered.
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
---
drivers/input/touchscreen/stmfts.c | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/drivers/input/touchscreen/stmfts.c b/drivers/input/touchscreen/stmfts.c
index 3613c7f2ab15..25d127aa8642 100644
--- a/drivers/input/touchscreen/stmfts.c
+++ b/drivers/input/touchscreen/stmfts.c
@@ -232,6 +232,12 @@ static void stmfts_report_contact_event(struct stmfts_data *sdata,
u8 orientation = event[6];
u8 area = event[7];
+ if (slot_id >= STMFTS_MAX_FINGERS) {
+ dev_warn(&sdata->client->dev,
+ "invalid slot ID %u\n", slot_id);
+ return;
+ }
+
input_mt_slot(sdata->input, slot_id);
input_mt_report_slot_state(sdata->input, MT_TOOL_FINGER, true);
@@ -250,6 +256,12 @@ static void stmfts_report_contact_release(struct stmfts_data *sdata,
{
u8 slot_id = (event[0] & STMFTS_MASK_TOUCH_ID) >> 4;
+ if (slot_id >= STMFTS_MAX_FINGERS) {
+ dev_warn(&sdata->client->dev,
+ "invalid slot ID %u\n", slot_id);
+ return;
+ }
+
input_mt_slot(sdata->input, slot_id);
input_mt_report_slot_inactive(sdata->input);
@@ -282,6 +294,12 @@ static void stmfts5_report_contact_event(struct stmfts_data *sdata,
int distance = 0;
unsigned int tool;
+ if (touch_id >= STMFTS_MAX_FINGERS) {
+ dev_warn(&sdata->client->dev,
+ "invalid slot ID %u\n", touch_id);
+ return;
+ }
+
switch (touch_type) {
case STMFTS_TOUCH_TYPE_STYLUS:
tool = MT_TOOL_PEN;
@@ -340,6 +358,12 @@ static void stmfts5_report_contact_release(struct stmfts_data *sdata,
/* format: touch ID is in high 4 bits of event[1] */
u8 touch_id = (event[1] & STMFTS_MASK_TOUCH_ID) >> 4;
+ if (touch_id >= STMFTS_MAX_FINGERS) {
+ dev_warn(&sdata->client->dev,
+ "invalid slot ID %u\n", touch_id);
+ return;
+ }
+
input_mt_slot(sdata->input, touch_id);
input_mt_report_slot_inactive(sdata->input);
}
--
2.56.0.385.gac671c819a-goog
next prev parent reply other threads:[~2026-11-03 22:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 22:58 [PATCH 0/3] Input: stmfts - event parsing and coordinate reporting fixes Dmitry Torokhov
2026-11-03 22:58 ` [PATCH 1/3] Input: stmfts - do not abort event parsing on non-touch events Dmitry Torokhov
2026-11-03 22:58 ` Dmitry Torokhov [this message]
2026-11-03 22:58 ` [PATCH 3/3] Input: stmfts - use touchscreen_report_pos() for coordinates Dmitry Torokhov
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=20261103225923.3892612-3-dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=andi.shyti@kernel.org \
--cc=david@ixit.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petr.hodina@protonmail.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
all inboxes | Powered by JetHome®