CVE-2026-64272
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-129
- Record status
- Modified
Affected
- Linux Kernel < 6.6.145
- Linux Kernel < 6.12.96
- Linux Kernel < 6.18.39
- Linux Kernel < 7.1.4
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-64272.md and follow it. Check whether this project is affected by CVE-2026-64272. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/112666835071d935fef764aab590339e97216d4a
- https://git.kernel.org/stable/c/75b12874b4172533b9efc349db328cb1a59c3981
- https://git.kernel.org/stable/c/7c00a0787af7164438bdbc97fcae9733cfc58d21
- https://git.kernel.org/stable/c/a6ac4e24c1a8a533bb61035184fdcc7eede4cc8d
- https://git.kernel.org/stable/c/a747c4eb02656afdbd92eea83b88e92715a23977
References
- https://git.kernel.org/stable/c/062bbe55a1f6d77b89d07135ba3b09f97bfac1cb
- https://git.kernel.org/stable/c/112666835071d935fef764aab590339e97216d4a
- https://git.kernel.org/stable/c/38de2979d90d8cd94f18e0567be4c8342d0e0410
- https://git.kernel.org/stable/c/75b12874b4172533b9efc349db328cb1a59c3981
- https://git.kernel.org/stable/c/7c00a0787af7164438bdbc97fcae9733cfc58d21
- https://git.kernel.org/stable/c/a6ac4e24c1a8a533bb61035184fdcc7eede4cc8d
- https://git.kernel.org/stable/c/a747c4eb02656afdbd92eea83b88e92715a23977