CVE-2026-64270

Input: mms114 - reject an oversized device packet size

HIGH
7.8
CVSS Score
Published: July 25, 2026 at 08:49 AM UTC
Updated: October 24, 2026 at 01:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: Input: mms114 - reject an oversized device packet size 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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.6 ≤ v < 6.6.1456.13 ≤ v < 6.18.396.19 ≤ v < 7.1.46.7 ≤ v < 6.12.963.67b8481d4aff73d6f451f25e74ea10240ff5131e
Vendor states this is fixed in 040843281eebfa110d08fd7fb083fe6cb55cea14 (fixed)
Vendor states this is fixed in 39b12daf1adb80f9595fdfe584961deb80860cbb (fixed)
Vendor states this is fixed in 5d2ea15ba03bf17ed143ff1a0995a4206edc3fb6 (fixed)
Vendor states this is fixed in 66725039f7090afe14c31bd259e2059a68f04023 (fixed)
Vendor states this is fixed in 8301c335305344d4da4ab9442b6a399dacfe5b8d (fixed)
Vendor states this is fixed in b78150729762d47c14fe29a2582bdca5568e62b8 (fixed)
Vendor states this is fixed in d99ba93c35ff2d5276e9c2632967481bd53a79d0 (fixed)
Vendor states this is fixed in f3d5e77b27fded71dcb97f409262bf0abba0410e (fixed)
Vendor states this is fixed in 3.6 (unaffected)
Vendor states this is fixed in 5.10.266 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.4 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card