# CVE-2026-64272: Input: mms114 - fix touch indexing for MMS134S and MMS136

> Incorrect touch event indexing in the mms114 driver causes data parsing errors for specific touch controllers, requiring a kernel patch.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jul 2026
- **Updated:** 23 Aug 2026
- **Also known as:** BELL-CVE-2026-64272, DEBIAN-CVE-2026-64272, GHSA-prw5-9985-9rc7, ROOT-OS-UBUNTU-2204-CVE-2026-64272, UBUNTU-CVE-2026-64272

## What is CVE-2026-64272?

CVE-2026-64272 is a high-severity vulnerability in Linux kernel, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

Input: mms114 - fix touch indexing for MMS134S and MMS136

The MMS134S and MMS136 touch controllers have an event size of 6 bytes
rather than 8 bytes. When __mms114_read_reg() reads the touch data
packet from the device into the touch buffer, the events are packed
tightly at 6-byte intervals. However, the driver iterates through the
events using standard C array indexing (touch[index]), where each
element is sizeof(struct mms114_touch) (8 bytes) apart. As a result, any
touch events beyond the first one are read from incorrect offsets and
parsed improperly.

Fix this by explicitly calculating the byte offset for each touch event
based on the device's specific event size.

Weakness: CWE-129 (Improper Validation of Array Index)

## Which versions are affected by CVE-2026-64272?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-64272?

Apply the vendor's patch.

## Is CVE-2026-64272 being exploited?

There is no known exploitation of CVE-2026-64272 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-64272 and fix it if it is affected.

What it is: CVE-2026-64272 is a high-severity vulnerability in Linux kernel, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64272 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-64272/ (Markdown: https://insights.sbomify.com/CVE-2026-64272/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-64272
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-64272
- OSV: https://osv.dev/vulnerability/CVE-2026-64272

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-64272/
Summaries are generated and may contain mistakes; the official description above is the record.