Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64272Input: mms114 - fix touch indexing for MMS134S and MMS136

Description

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

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64272, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 53fefdd1d3a3403d8c44e28898d1031d8763b913 – < 062bbe55a1f6d77b89d07135ba3b09f97bfac1cb
    • affected 53fefdd1d3a3403d8c44e28898d1031d8763b913 – < 38de2979d90d8cd94f18e0567be4c8342d0e0410
    • affected 53fefdd1d3a3403d8c44e28898d1031d8763b913 – < 112666835071d935fef764aab590339e97216d4a
    • affected 53fefdd1d3a3403d8c44e28898d1031d8763b913 – < 7c00a0787af7164438bdbc97fcae9733cfc58d21
    • affected 53fefdd1d3a3403d8c44e28898d1031d8763b913 – < 75b12874b4172533b9efc349db328cb1a59c3981
    • affected 53fefdd1d3a3403d8c44e28898d1031d8763b913 – < a747c4eb02656afdbd92eea83b88e92715a23977
    • affected 53fefdd1d3a3403d8c44e28898d1031d8763b913 – < a6ac4e24c1a8a533bb61035184fdcc7eede4cc8d
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.15.217 – ≤ 5.15.*
    • unaffected 6.1.184 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64272 badge
[![CVE-2026-64272](https://cveledger.app/badge/CVE-2026-64272.svg)](https://cveledger.app/cve/CVE-2026-64272)

Record last updated .