Input: mms114 - fix touch indexing for MMS134S and MMS136
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.13
References 7
git.kernel.org
- stable/c/062bbe55a1f6d77b89d07135ba3b09f97bfac1cb
- stable/c/38de2979d90d8cd94f18e0567be4c8342d0e0410
- stable/c/112666835071d935fef764aab590339e97216d4a
- stable/c/7c00a0787af7164438bdbc97fcae9733cfc58d21
- stable/c/75b12874b4172533b9efc349db328cb1a59c3981
- stable/c/a747c4eb02656afdbd92eea83b88e92715a23977
- stable/c/a6ac4e24c1a8a533bb61035184fdcc7eede4cc8d