CVE-2026-64270

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

Input: mms114 - reject an oversized device packet size

mms114_interrupt() reads a packet of touch data from the device into a fixed-size on-stack buffer

struct mms114_touch touch[MMS114_MAX_TOUCH];

which holds MMS114_MAX_TOUCH (10) events of MMS114_EVENT_SIZE (8) bytes, i.e. 80 bytes. The length of the I2C read into it is taken verbatim from the device:

packet_size = mms114_read_reg(data, MMS114_PACKET_SIZE); if (packet_size <= 0) goto out; ... error = __mms114_read_reg(data, MMS114_INFORMATION, packet_size, (u8 *)touch);

packet_size is a single device register byte (0x0F) and the only check is the lower bound packet_size <= 0; it is never bounded against the size of touch[]. A malfunctioning, malicious or counterfeit controller (or an attacker tampering with the I2C bus) can report a packet_size of up to 255, so __mms114_read_reg() writes up to 175 bytes past the end of touch[] on the IRQ-thread stack: a stack out-of-bounds write that can overwrite the stack canary, saved registers and the return address.

A well-formed device never reports more than the buffer holds, so reject an oversized packet and drop the report, consistent with the handler's other error paths, rather than reading past the buffer.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 23, 2026

Advisory Details (5)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

Input: mms114 - reject an oversized device packet size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f3d5e77b27fded71dcb97f409262bf0abba0410e
generic

Input: mms114 - reject an oversized device packet size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b78150729762d47c14fe29a2582bdca5568e62b8
generic

Input: mms114 - reject an oversized device packet size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8301c335305344d4da4ab9442b6a399dacfe5b8d
generic

Input: mms114 - reject an oversized device packet size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66725039f7090afe14c31bd259e2059a68f04023
generic

Input: mms114 - reject an oversized device packet size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d2ea15ba03bf17ed143ff1a0995a4206edc3fb6

Vendor Advisories for CVE-2026-64270(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (338 versions)
linux-6.126.12.100-1~deb12u1
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (500 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 23× in last 7d / 77× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:12 UTCEG score recompute
  3. 2026-08-30 00:12 UTCGHSA enrichment
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 21:06 UTCEG score recompute
  6. 2026-08-27 21:06 UTCGHSA enrichment
  7. 2026-08-27 03:11 UTCGHSA enrichment
  8. 2026-08-26 14:56 UTCEG score recompute
  9. 2026-08-26 14:56 UTCGHSA enrichment
  10. 2026-08-26 14:47 UTCEPSS rescore
  11. 2026-08-26 02:41 UTCGHSA enrichment
  12. 2026-08-25 14:25 UTCEG score recompute
  13. 2026-08-25 14:25 UTCGHSA enrichment
  14. 2026-08-25 13:49 UTCEPSS rescore
  15. 2026-08-25 02:06 UTCEG score recompute
  16. 2026-08-25 02:06 UTCGHSA enrichment
  17. 2026-08-24 13:51 UTCEG score recompute
  18. 2026-08-24 13:51 UTCGHSA enrichment
  19. 2026-08-24 01:36 UTCGHSA enrichment
  20. 2026-08-23 13:21 UTCGHSA enrichment
  21. 2026-08-23 13:09 UTCGHSA enrichment
  22. 2026-08-23 12:32 UTCEG score recompute
  23. 2026-08-23 12:32 UTCGHSA enrichment
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-23 00:17 UTCGHSA enrichment
Show 70 more
  1. 2026-08-22 12:01 UTCEG score recompute
  2. 2026-08-22 12:01 UTCGHSA enrichment
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-21 23:44 UTCGHSA enrichment
  5. 2026-08-21 11:29 UTCGHSA enrichment
  6. 2026-08-20 22:49 UTCGHSA enrichment
  7. 2026-08-20 10:34 UTCGHSA enrichment
  8. 2026-08-19 22:19 UTCEG score recompute
  9. 2026-08-19 22:19 UTCGHSA enrichment
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-19 10:03 UTCGHSA enrichment
  12. 2026-08-18 21:46 UTCEG score recompute
  13. 2026-08-18 21:46 UTCGHSA enrichment
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-18 08:50 UTCGHSA enrichment
  16. 2026-08-17 20:20 UTCEG score recompute
  17. 2026-08-17 20:20 UTCGHSA enrichment
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-17 05:21 UTCGHSA enrichment
  20. 2026-08-16 20:01 UTCEG score recompute
  21. 2026-08-16 20:01 UTCGHSA enrichment
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 07:45 UTCEG score recompute
  24. 2026-08-16 07:45 UTCGHSA enrichment
  25. 2026-08-15 19:31 UTCGHSA enrichment
  26. 2026-08-15 07:16 UTCEG score recompute
  27. 2026-08-15 07:16 UTCGHSA enrichment
  28. 2026-08-15 01:30 UTCEPSS rescore
  29. 2026-08-14 19:00 UTCGHSA enrichment
  30. 2026-08-14 06:45 UTCEG score recompute
  31. 2026-08-14 06:45 UTCGHSA enrichment
  32. 2026-08-13 22:00 UTCEPSS rescore
  33. 2026-08-13 18:30 UTCEG score recompute 7.80
  34. 2026-08-13 18:30 UTCGHSA enrichment
  35. 2026-08-13 18:30 UTCNVD updateCVSS v3 → 7.8 · severity → HIGH
  36. 2026-08-13 14:06 UTCGHSA enrichment
  37. 2026-08-12 13:51 UTCEPSS rescore
  38. 2026-08-11 00:00 UTCEPSS rescore
  39. 2026-08-10 19:09 UTCGHSA enrichment
  40. 2026-08-09 13:47 UTCEPSS rescore
  41. 2026-08-08 16:37 UTCEPSS rescore
  42. 2026-08-08 00:11 UTCGHSA enrichment
  43. 2026-08-06 13:47 UTCEPSS rescore
  44. 2026-08-05 19:17 UTCEPSS rescore
  45. 2026-08-05 19:17 UTCEPSS rescore
  46. 2026-08-05 05:14 UTCGHSA enrichment
  47. 2026-08-04 15:10 UTCEPSS rescore
  48. 2026-08-04 10:39 UTCEPSS rescore
  49. 2026-08-03 10:36 UTCEPSS rescore
  50. 2026-08-02 10:13 UTCGHSA enrichment
  51. 2026-08-02 02:27 UTCEPSS rescore
  52. 2026-08-01 04:16 UTCEPSS rescore
  53. 2026-07-30 16:28 UTCEPSS rescore
  54. 2026-07-30 15:16 UTCEG score recompute
  55. 2026-07-30 15:16 UTCGHSA enrichment
  56. 2026-07-30 01:30 UTCEPSS rescore
  57. 2026-07-30 01:30 UTCEPSS rescore
  58. 2026-07-28 22:11 UTCEG score recompute
  59. 2026-07-28 22:11 UTCGHSA enrichment
  60. 2026-07-28 15:37 UTCEPSS rescore
  61. 2026-07-27 14:14 UTCEPSS rescore
  62. 2026-07-26 14:54 UTCEPSS rescore
  63. 2026-07-26 14:54 UTCEPSS rescore
  64. 2026-07-26 02:54 UTCEG score recompute
  65. 2026-07-26 02:53 UTCGHSA enrichment
  66. 2026-07-25 14:18 UTCEPSS rescore
  67. 2026-07-25 14:18 UTCEPSS rescore
  68. 2026-07-25 10:39 UTCNVD update
  69. 2026-07-25 09:41 UTCEG score recompute
  70. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64270?
CVE-2026-64270 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: Input: mms114 - reject an oversized device packet size mms114_interrupt() reads a packet of touch data from the device into a fixed-size on-stack buffer struct mms114touch touch[MMS114MAX_TOUCH]; which holds MMS114MAXTOUCH (10)…
When was CVE-2026-64270 disclosed?
CVE-2026-64270 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64270 actively exploited?
CVE-2026-64270 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64270?
CVE-2026-64270 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64270?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64270, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64270

Explore →

Is Your Infrastructure Affected by CVE-2026-64270?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.