Input: mms114 - fix touch indexing for MMS134S and MMS136
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 53fefdd1d3a3403d8c44e28898d1031d8763b913 · < a747c4eb02656afdbd92eea83b88e92715a23977| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel mms114 driver uses incorrect offsets when parsing touch events beyond the first event from MMS134S and MMS136 controllers. An attacker’s ability to trigger or exploit this issue is not described; the input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with the mms114 driver and MMS134S or MMS136 touch controllers should check their systems; affected versions are not specified.