Input: mms114 - reject an oversized device packet size
Summary
| CVE | CVE-2026-64270 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-07-25 10:17:07 UTC |
| Updated | 2026-07-30 15:00:27 UTC |
| 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. |
Risk And Classification
EPSS: 0.002000000 probability, percentile 0.100850000 (date 2026-08-03)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 07b8481d4aff73d6f451f25e74ea10240ff5131e 5d2ea15ba03bf17ed143ff1a0995a4206edc3fb6 git | Not specified |
| CNA | Linux | Linux | affected 07b8481d4aff73d6f451f25e74ea10240ff5131e b78150729762d47c14fe29a2582bdca5568e62b8 git | Not specified |
| CNA | Linux | Linux | affected 07b8481d4aff73d6f451f25e74ea10240ff5131e 8301c335305344d4da4ab9442b6a399dacfe5b8d git | Not specified |
| CNA | Linux | Linux | affected 07b8481d4aff73d6f451f25e74ea10240ff5131e f3d5e77b27fded71dcb97f409262bf0abba0410e git | Not specified |
| CNA | Linux | Linux | affected 07b8481d4aff73d6f451f25e74ea10240ff5131e 66725039f7090afe14c31bd259e2059a68f04023 git | Not specified |
| CNA | Linux | Linux | affected 3.6 | Not specified |
| CNA | Linux | Linux | unaffected 3.6 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.145 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.96 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.39 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.4 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2-rc1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/66725039f7090afe14c31bd259e2059a68f04023 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/f3d5e77b27fded71dcb97f409262bf0abba0410e | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/8301c335305344d4da4ab9442b6a399dacfe5b8d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/b78150729762d47c14fe29a2582bdca5568e62b8 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/5d2ea15ba03bf17ed143ff1a0995a4206edc3fb6 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.