Linux kernel -stable discussions
 help / color / mirror / Atom feed
* [PATCH v2] Input: tca8418_keypad - fix potential infinite loop and OOB access on invalid keycodes
       [not found] <f03a892c-0961-4e07-a6e1-dbc3ff2064db@gmail.com>
@ 2026-07-25  8:09 ` Liang Zhan
  2026-07-26  4:41   ` Dmitry Torokhov
  0 siblings, 1 reply; 3+ messages in thread
From: Liang Zhan @ 2026-07-25  8:09 UTC (permalink / raw)
  To: dmitry.torokhov; +Cc: linux-input, linux-kernel, stable

The current code checks the raw register value against zero to detect an 
empty FIFO. However, the TCA8418 datasheet defines key code 0 as the 
empty-FIFO condition. If the hardware returns garbage data, the loop may 
never terminate and the extracted keycode can cause an out-of-bounds 
access on keymap[].

Move the empty-FIFO check to operate on the extracted key code so that
the loop terminates correctly. Additionally, validate row/column indices
against the configured matrix dimensions before indexing into the
keymap array, skipping invalid events.

Cc: stable@vger.kernel.org
Signed-off-by: Zhian Liang <liangzhan5dev@gmail.com>
---
changes in v2:
- Moved empty-FIFO check to operate on extracted key code instead of
   raw register value.
- Added row/col validation against configured matrix dimensions.
- Dropped explicit 0xFF check as requested.
---
  drivers/input/keyboard/tca8418_keypad.c | 19 ++++++++++++++++---
  1 file changed, 16 insertions(+), 3 deletions(-)

diff --git a/drivers/input/keyboard/tca8418_keypad.c 
b/drivers/input/keyboard/tca8418_keypad.c
index b124e576feca..36d4a7c38bb1 100644
--- a/drivers/input/keyboard/tca8418_keypad.c
+++ b/drivers/input/keyboard/tca8418_keypad.c
@@ -114,6 +114,8 @@ struct tca8418_keypad {
  	struct input_dev *input;

  	unsigned int row_shift;
+	unsigned int rows;
+	unsigned int cols;
  };

  /*
@@ -171,19 +173,28 @@ static void tca8418_read_keypad(struct 
tca8418_keypad *keypad_data)
  			break;
  		}

-		/* Assume that key code 0 signifies empty FIFO */
-		if (reg <= 0)
-			break;

  		state = reg & KEY_EVENT_VALUE;
  		code  = reg & KEY_EVENT_CODE;

+		/* Key code 0 signifies empty FIFO */
+		if (!code)
+			break;
+
  		row = code / TCA8418_MAX_COLS;
  		col = code % TCA8418_MAX_COLS;

  		row = (col) ? row : row - 1;
  		col = (col) ? col - 1 : TCA8418_MAX_COLS - 1;

+		/* Validate against configured matrix size */
+		if (row >= keypad_data->rows || col >= keypad_data->cols) {
+			dev_err(&keypad_data->client->dev,
+				"invalid key code %d (row %d, col %d)\n",
+				code, row, col);
+			continue;
+		}
+
  		code = MATRIX_SCAN_CODE(row, col, keypad_data->row_shift);
  		input_event(input, EV_MSC, MSC_SCAN, code);
  		input_report_key(input, keymap[code], state);
@@ -298,6 +309,8 @@ static int tca8418_keypad_probe(struct i2c_client 
*client)

  	keypad_data->client = client;
  	keypad_data->row_shift = row_shift;
+	keypad_data->rows = rows;
+	keypad_data->cols = cols;

  	/* Read key lock register, if this fails assume device not present */
  	error = tca8418_read_byte(keypad_data, REG_KEY_LCK_EC, &reg);
-- 
2.34.1


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH v2] Input: tca8418_keypad - fix potential infinite loop and OOB access on invalid keycodes
  2026-07-25  8:09 ` [PATCH v2] Input: tca8418_keypad - fix potential infinite loop and OOB access on invalid keycodes Liang Zhan
@ 2026-07-26  4:41   ` Dmitry Torokhov
  2026-07-26 11:57     ` Zhan Liang
  0 siblings, 1 reply; 3+ messages in thread
From: Dmitry Torokhov @ 2026-07-26  4:41 UTC (permalink / raw)
  To: Liang Zhan; +Cc: linux-input, linux-kernel, stable

On Sat, Jul 25, 2026 at 04:09:47PM +0800, Liang Zhan wrote:
> The current code checks the raw register value against zero to detect an
> empty FIFO. However, the TCA8418 datasheet defines key code 0 as the
> empty-FIFO condition. If the hardware returns garbage data, the loop may
> never terminate and the extracted keycode can cause an out-of-bounds access
> on keymap[].
> 
> Move the empty-FIFO check to operate on the extracted key code so that
> the loop terminates correctly. Additionally, validate row/column indices
> against the configured matrix dimensions before indexing into the
> keymap array, skipping invalid events.

Unfortunately your mailer line-wrapped the patch so it does not apply. 

Thanks.

-- 
Dmitry

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH v2] Input: tca8418_keypad - fix potential infinite loop and OOB access on invalid keycodes
  2026-07-26  4:41   ` Dmitry Torokhov
@ 2026-07-26 11:57     ` Zhan Liang
  0 siblings, 0 replies; 3+ messages in thread
From: Zhan Liang @ 2026-07-26 11:57 UTC (permalink / raw)
  To: Dmitry Torokhov; +Cc: linux-input, linux-kernel, stable

Hi Dmitry,
v3 was sent here:
https://lore.kernel.org/linux-input/20260726112658.37D911F00A3A@smtp.kernel.org/T/#t
It broke the thread because I forgot --in-reply-to. Sorry for the noise.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-07-26 11:57 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <f03a892c-0961-4e07-a6e1-dbc3ff2064db@gmail.com>
2026-07-25  8:09 ` [PATCH v2] Input: tca8418_keypad - fix potential infinite loop and OOB access on invalid keycodes Liang Zhan
2026-07-26  4:41   ` Dmitry Torokhov
2026-07-26 11:57     ` Zhan Liang

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox