CVE-2026-64270

What the bug is

mms114_interrupt() reads a packet of touch data from the device into a fixed-size on-stack buffer struct mms114_touch touch[MMS114_MAX_TOUCH]; which holds MMS114_MAX_TOUCH (10) events of MMS114_EVENT_SIZE (8) bytes, i.e. 80 bytes. The length of the I2C read into it is taken verbatim from the device: packet_size = mms114_read_reg(data, MMS114_PACKET_SIZE); if (packet_size <= 0) goto out; ... error = __mms114_read_reg(data, MMS114_INFORMATION, packet_size, (u8 *)touch); packet_size is a single device register byte (0x0F) and the only check is the lower bound packet_size <= 0; it is never bounded against the size of touch[]. A malfunctioning, malicious or counterfeit controller (or an attacker tampering with the I2C bus) can report a packet_size of up to 255, so __mms114_read_reg() writes up to 175 bytes past the end of touch[] on the IRQ-thread stack: a stack out-of-bounds write that can overwrite the stack canary, saved registers and the return address. A well-formed device never reports more than the buffer holds, so reject an oversized packet and drop the report, consistent with the handler's other error paths, rather than reading past the buffer.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/input/touchscreen/mms114.c

What this is

INPUT (KEYBOARD, MOUSE, JOYSTICK, TOUCHSCREEN) DRIVERSMAINTAINERS section matched on drivers/input/ · linux-input@vger.kernel.org · Maintained

Kernel module

none to look for. The file would have gone into mms114, and Debian does not compile it into that module, so finding mms114 in lsmod would say nothing about this CVE.

Check it on the machine

grep -wE 'CONFIG_INPUT|CONFIG_INPUT_TOUCHSCREEN|CONFIG_TOUCHSCREEN_MMS114' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian does not build this code. In 5 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.

• bookworm, trixie, forky, sid, bookworm · linux-6.12n

n

not enabled on any flavour - this release does not build the code

Build switches

CONFIG_INPUT, CONFIG_INPUT_TOUCHSCREEN, CONFIG_TOUCHSCREEN_MMS114

Reads as

all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published

2026-07-25 (3 months ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.17%, higher than 5.8% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

not yet assignedsource

Subsystem

drivers/input

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

Introduced	Fixed in	Commit
3.6	5.10.266	040843281eeb
3.6	5.15.217	39b12daf1adb
3.6	6.1.184	d99ba93c35ff
3.6	6.6.145	5d2ea15ba03b
3.6	6.12.96	b78150729762
3.6	6.18.39	8301c3353053
3.6	7.1.4	f3d5e77b27fd
3.6	7.2	66725039f709

Debian advisories