In the Linux kernel, the following vulnerability has been resolved: Input: mms114 - fix touch indexing for MMS134S and MMS136 The MMS134S and MMS136… (CVE-2026-64272)
A vulnerability in the Linux kernel's mms114 touch controller driver was fixed to correct improper parsing of touch events for MMS134S and MMS136 devices. The issue arose because the driver incorrectly assumed each touch event was 8 bytes, while the actual event size is 6 bytes, causing misaligned reads beyond the first event. This could lead to incorrect touch data processing.
AI Analysis
Technical Summary
The Linux kernel mms114 driver mishandled touch event data from MMS134S and MMS136 controllers due to a mismatch between the expected event size (8 bytes) and the actual event size (6 bytes). The driver used standard C array indexing assuming 8-byte intervals, resulting in incorrect offsets and improper parsing of events beyond the first. The vulnerability was resolved by explicitly calculating byte offsets based on the device's specific 6-byte event size, ensuring correct event indexing and parsing.
Potential Impact
Improper parsing of touch events could cause incorrect touch input data to be processed by the system. The input data misinterpretation may affect device functionality relying on accurate touch input. There is no indication of code execution, privilege escalation, or data leakage from the provided information.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to explicitly calculate the correct byte offset for each touch event based on the device's event size. Users should update to the fixed kernel version containing this patch. Patch status is not explicitly confirmed; check the Linux kernel vendor advisory for the current remediation status and apply official fixes as available.
In the Linux kernel, the following vulnerability has been resolved: Input: mms114 - fix touch indexing for MMS134S and MMS136 The MMS134S and MMS136… (CVE-2026-64272)
Description
A vulnerability in the Linux kernel's mms114 touch controller driver was fixed to correct improper parsing of touch events for MMS134S and MMS136 devices. The issue arose because the driver incorrectly assumed each touch event was 8 bytes, while the actual event size is 6 bytes, causing misaligned reads beyond the first event. This could lead to incorrect touch data processing.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel mms114 driver mishandled touch event data from MMS134S and MMS136 controllers due to a mismatch between the expected event size (8 bytes) and the actual event size (6 bytes). The driver used standard C array indexing assuming 8-byte intervals, resulting in incorrect offsets and improper parsing of events beyond the first. The vulnerability was resolved by explicitly calculating byte offsets based on the device's specific 6-byte event size, ensuring correct event indexing and parsing.
Potential Impact
Improper parsing of touch events could cause incorrect touch input data to be processed by the system. The input data misinterpretation may affect device functionality relying on accurate touch input. There is no indication of code execution, privilege escalation, or data leakage from the provided information.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to explicitly calculate the correct byte offset for each touch event based on the device's event size. Users should update to the fixed kernel version containing this patch. Patch status is not explicitly confirmed; check the Linux kernel vendor advisory for the current remediation status and apply official fixes as available.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-prw5-9985-9rc7
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64272"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420e9c2644c7f8086617
Added to database: 07/25/2026, 23:09:02 UTC
Last enriched: 07/25/2026, 23:41:23 UTC
Last updated: 07/26/2026, 03:45:01 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.