Answer in brief
CVE-2026-64272 records a High severity (CVSS 7.8) vulnerability in Input: mms114 - fix touch indexing for MMS134S and MMS136. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=53fefdd1d3a3403d8c44e28898d1031d8763b913 <112666835071d935fef764aab590339e97216d4a || >=53fefdd1d3a3403d8c44e28898d1031d8763b913 <7c00a0787af7164438bdbc97fcae9733cfc58d21 || >=53fefdd1d3a3403d8c44e28898d1031d8763b913 <75b12874b4172533b9efc349db328cb1a59c3981 || >=53fefdd1d3a3403d8c44e28898d1031d8763b913 <a747c4eb02656afdbd92eea83b88e92715a23977 || >=53fefdd1d3a3403d8c44e28898d1031d8763b913 <a6ac4e24c1a8a533bb61035184fdcc7eede4cc8d | 112666835071d935fef764aab590339e97216d4a, 7c00a0787af7164438bdbc97fcae9733cfc58d21, 75b12874b4172533b9efc349db328cb1a59c3981, a747c4eb02656afdbd92eea83b88e92715a23977, a6ac4e24c1a8a533bb61035184fdcc7eede4cc8d |
| Linux/Linuxgeneric | 5.13 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 14, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64272 records a High severity (CVSS 7.8) vulnerability in Input: mms114 - fix touch indexing for MMS134S and MMS136. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=53fefdd1d3a3403d8c44e28898d1031d8763b913 <112666835071d935fef764aab590339e97216d4a || >=53fefdd1d3a3403d8c44e28898d1031d8763b913 <7c00a0787af7164438bdbc97fcae9733cfc58d21 || >=53fefdd1d3a3403d8c44e28898d1031d8763b913 <75b12874b4172533b9efc349db328cb1a59c3981 || >=53fefdd1d3a3403d8c44e28898d1031d8763b913 <a747c4eb02656afdbd92eea83b88e92715a23977 || >=53fefdd1d3a3403d8c44e28898d1031d8763b913 <a6ac4e24c1a8a533bb61035184fdcc7eede4cc8d | 112666835071d935fef764aab590339e97216d4a, 7c00a0787af7164438bdbc97fcae9733cfc58d21, 75b12874b4172533b9efc349db328cb1a59c3981, a747c4eb02656afdbd92eea83b88e92715a23977, a6ac4e24c1a8a533bb61035184fdcc7eede4cc8d |
| Linux/Linuxgeneric | 5.13 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 14, 2026
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.
Quoted source text, attributed separately from HOL analysis.