CVE-2026-64272: Input: mms114 - fix touch indexing for MMS134S and MMS136
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 062bbe55a1f6d77b89d07135ba3b09f97bfac1cb, 112666835071d935fef764aab590339e97216d4a, 38de2979d90d8cd94f18e0567be4c8342d0e0410.
Low priority for now. Upgrade to Linux Linux 062bbe55a1f6d77b89d07135ba3b09f97bfac1cb, 112666835071d935fef764aab590339e97216d4a, 38de2979d90d8cd94f18e0567be4c8342d0e0410 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 25, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-129
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.13 and later · before 6.6.145
- linux linux kernel6.7 and later · before 6.12.96
- linux linux kernel6.13 and later · before 6.18.39
- linux linux kernel6.19 and later · before 7.1.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.13affected
- 53fefdd1d3a3403d8c44e28898d1031d8763b913 and later · before 062bbe55a1f6d77b89d07135ba3b09f97bfac1cbaffected · git
- 53fefdd1d3a3403d8c44e28898d1031d8763b913 and later · before 38de2979d90d8cd94f18e0567be4c8342d0e0410affected · git
- 53fefdd1d3a3403d8c44e28898d1031d8763b913 and later · before 112666835071d935fef764aab590339e97216d4aaffected · git
- 53fefdd1d3a3403d8c44e28898d1031d8763b913 and later · before 7c00a0787af7164438bdbc97fcae9733cfc58d21affected · git
- 53fefdd1d3a3403d8c44e28898d1031d8763b913 and later · before 75b12874b4172533b9efc349db328cb1a59c3981affected · git
- 53fefdd1d3a3403d8c44e28898d1031d8763b913 and later · before a747c4eb02656afdbd92eea83b88e92715a23977affected · git
- 53fefdd1d3a3403d8c44e28898d1031d8763b913 and later · before a6ac4e24c1a8a533bb61035184fdcc7eede4cc8daffected · git
- before 5.13not affected · semver
- 5.15.217 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-64270Jul 25, 2026 · Input: mms114 - reject an oversized device packet size31Monitor
- ← EarlierCVE-2026-64271Jul 25, 2026 · Input: touchwin - reset the packet index on every complete packet31Monitor
- Later →CVE-2026-64273Jul 25, 2026 · Input: iforce - bound the device-reported force-feedback effect index31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 062bbe55a1f6d77b89d07135ba3b09f97bfac1cb | Vendor (CNA) |
| Linux Linux | 112666835071d935fef764aab590339e97216d4a | Vendor (CNA) |
| Linux Linux | 38de2979d90d8cd94f18e0567be4c8342d0e0410 | Vendor (CNA) |
| Linux Linux | 75b12874b4172533b9efc349db328cb1a59c3981 | Vendor (CNA) |
| Linux Linux | 7c00a0787af7164438bdbc97fcae9733cfc58d21 | Vendor (CNA) |
| Linux Linux | a6ac4e24c1a8a533bb61035184fdcc7eede4cc8d | Vendor (CNA) |
| Linux Linux | a747c4eb02656afdbd92eea83b88e92715a23977 | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-640186 days apartnet: mana: validate rx_req_idx to prevent out-of-bounds array access37Monitor
- CVE-2026-4311080 days apartwifi: brcmfmac: validate bsscfg indices in IF events35Monitor
- CVE-2026-4317280 days apartwifi: iwlwifi: fix 22000 series SMEM parsing35Monitor
- CVE-2026-23246129 days apartwifi: mac80211: bounds-check link_id in ieee80211_ml_reconfiguration35Monitor
- CVE-2026-642730 days apartInput: iforce - bound the device-reported force-feedback effect index31Monitor
- CVE-2026-643300 days apartusb: typec: tcpm: Validate SVID index in svdm_consume_modes()31Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-129 · Improper Validation of Array IndexCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/112666835071d935fef764aab590339e97216d4a
- git.kernel.org/stable/c/38de2979d90d8cd94f18e0567be4c8342d0e0410
- git.kernel.org/stable/c/75b12874b4172533b9efc349db328cb1a59c3981
- git.kernel.org/stable/c/7c00a0787af7164438bdbc97fcae9733cfc58d21
- git.kernel.org/stable/c/a6ac4e24c1a8a533bb61035184fdcc7eede4cc8d
- git.kernel.org/stable/c/a747c4eb02656afdbd92eea83b88e92715a23977
Vendor advisories and official records. Exploit/PoC links are deliberately left out.