CVE-2026-64274

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: goodix - clamp the device-reported contact count

goodix_ts_read_input_report() copies the number of touch points reported by the device into an on-stack buffer

u8 point_data[2 + GOODIX_MAX_CONTACT_SIZE * GOODIX_MAX_CONTACTS];

which is sized for at most GOODIX_MAX_CONTACTS (10) contacts. The only runtime check bounds the per-interrupt count against ts->max_touch_num, but that value is taken verbatim from a 4-bit field of the device configuration block and is never clamped:

ts->max_touch_num = ts->config[MAX_CONTACTS_LOC] & 0x0f;

The nibble can be 0..15, so a malfunctioning, malicious or counterfeit controller (or an attacker tampering with the I2C bus) can advertise up to 15 contacts. goodix_ts_read_input_report() then accepts a touch_num of up to 15 and the second goodix_i2c_read() writes ts->contact_size * (touch_num - 1) bytes past the one-contact header into point_data - up to 30 bytes (45 with the 9-byte report format) beyond the 92-byte buffer: a stack out-of-bounds write.

Clamp max_touch_num to GOODIX_MAX_CONTACTS, the number of contacts point_data[] is sized for, when reading it from the configuration.

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 17, 2026

Advisory Details (8)

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

Input: goodix - clamp the device-reported contact count - kernel/git/stable/linux.git - Linux kernel stable tree

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

Input: goodix - clamp the device-reported contact count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98b2caef249183b572c04451365246f919707845
generic

Input: goodix - clamp the device-reported contact count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/719d1a2c83a46be6bf81af905e4f6adb3d32dc28
generic

Input: goodix - clamp the device-reported contact count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5ed62a96e06be4e94b8296b7932afee550a70e04
generic

Input: goodix - clamp the device-reported contact count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4bfea9c3a0981c1c7fc5d1a1b27197b2de247902
generic

Input: goodix - clamp the device-reported contact count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/46addbd13dbf4aacb71cfbca964a5e552d0f45ae
generic

Input: goodix - clamp the device-reported contact count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b32303460155603d25444274856013d211d5e1f
generic

Input: goodix - clamp the device-reported contact count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2a67668690129953e898923260a2dd1c7c196495

Vendor Advisories for CVE-2026-64274(2)

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

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1
linux-6.126.12.100-1~deb12u1
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 19× in last 7d / 75× 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:13 UTCEG score recompute
  3. 2026-08-30 00:12 UTCGHSA enrichment
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 21:51 UTCEG score recompute
  6. 2026-08-27 21:51 UTCGHSA enrichment
  7. 2026-08-27 09:58 UTCGHSA enrichment
  8. 2026-08-26 19:51 UTCEG score recompute
  9. 2026-08-26 19:51 UTCGHSA enrichment
  10. 2026-08-26 14:47 UTCEPSS rescore
  11. 2026-08-26 07:10 UTCGHSA enrichment
  12. 2026-08-25 19:16 UTCEG score recompute
  13. 2026-08-25 19:16 UTCGHSA enrichment
  14. 2026-08-25 13:49 UTCEPSS rescore
  15. 2026-08-25 07:23 UTCGHSA enrichment
  16. 2026-08-24 19:30 UTCEG score recompute
  17. 2026-08-24 19:30 UTCGHSA enrichment
  18. 2026-08-24 07:33 UTCGHSA enrichment
  19. 2026-08-23 19:24 UTCGHSA enrichment
  20. 2026-08-23 07:31 UTCEG score recompute
  21. 2026-08-23 07:31 UTCGHSA enrichment
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-22 19:35 UTCGHSA enrichment
  24. 2026-08-22 07:42 UTCEG score recompute
  25. 2026-08-22 07:42 UTCGHSA enrichment
Show 68 more
  1. 2026-08-21 23:49 UTCEPSS rescore
  2. 2026-08-21 19:49 UTCGHSA enrichment
  3. 2026-08-21 07:56 UTCEG score recompute
  4. 2026-08-21 07:56 UTCGHSA enrichment
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 20:02 UTCGHSA enrichment
  7. 2026-08-20 08:09 UTCGHSA enrichment
  8. 2026-08-19 20:16 UTCEG score recompute
  9. 2026-08-19 20:16 UTCGHSA enrichment
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-19 06:49 UTCGHSA enrichment
  12. 2026-08-18 18:51 UTCEG score recompute
  13. 2026-08-18 18:51 UTCGHSA enrichment
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-18 05:10 UTCGHSA enrichment
  16. 2026-08-17 17:14 UTCEG score recompute
  17. 2026-08-17 17:14 UTCGHSA enrichment
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-17 05:21 UTCGHSA enrichment
  20. 2026-08-16 19:01 UTCEG score recompute
  21. 2026-08-16 19:01 UTCGHSA enrichment
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 06:49 UTCEG score recompute
  24. 2026-08-16 06:49 UTCGHSA enrichment
  25. 2026-08-15 18:57 UTCGHSA enrichment
  26. 2026-08-15 07:04 UTCEG score recompute
  27. 2026-08-15 07:04 UTCGHSA enrichment
  28. 2026-08-15 01:30 UTCEPSS rescore
  29. 2026-08-14 18:16 UTCGHSA enrichment
  30. 2026-08-14 06:23 UTCEG score recompute
  31. 2026-08-14 06:23 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-12 13:51 UTCEPSS rescore
  37. 2026-08-11 13:27 UTCGHSA enrichment
  38. 2026-08-11 00:00 UTCEPSS rescore
  39. 2026-08-09 13:47 UTCEPSS rescore
  40. 2026-08-08 16:37 UTCEPSS rescore
  41. 2026-08-08 13:55 UTCGHSA enrichment
  42. 2026-08-05 19:17 UTCEPSS rescore
  43. 2026-08-05 19:17 UTCEPSS rescore
  44. 2026-08-05 14:22 UTCGHSA enrichment
  45. 2026-08-04 15:10 UTCEPSS rescore
  46. 2026-08-04 10:39 UTCEPSS rescore
  47. 2026-08-03 10:36 UTCEPSS rescore
  48. 2026-08-02 14:49 UTCGHSA enrichment
  49. 2026-08-02 02:27 UTCEPSS rescore
  50. 2026-08-01 04:16 UTCEPSS rescore
  51. 2026-07-30 16:28 UTCEPSS rescore
  52. 2026-07-30 15:16 UTCEG score recompute
  53. 2026-07-30 15:16 UTCGHSA enrichment
  54. 2026-07-30 01:30 UTCEPSS rescore
  55. 2026-07-30 01:30 UTCEPSS rescore
  56. 2026-07-29 02:27 UTCEG score recompute
  57. 2026-07-29 02:27 UTCGHSA enrichment
  58. 2026-07-28 15:37 UTCEPSS rescore
  59. 2026-07-27 14:14 UTCEPSS rescore
  60. 2026-07-26 14:54 UTCEPSS rescore
  61. 2026-07-26 14:54 UTCEPSS rescore
  62. 2026-07-26 02:54 UTCEG score recompute
  63. 2026-07-26 02:53 UTCGHSA enrichment
  64. 2026-07-25 14:18 UTCEPSS rescore
  65. 2026-07-25 14:18 UTCEPSS rescore
  66. 2026-07-25 10:39 UTCNVD update
  67. 2026-07-25 09:41 UTCEG score recompute
  68. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64274?
CVE-2026-64274 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: Input: goodix - clamp the device-reported contact count goodixtsreadinputreport() copies the number of touch points reported by the device into an on-stack buffer u8 pointdata[2 + GOODIXMAXCONTACTSIZE * GOODIXMAXCONTACTS]; which is…
When was CVE-2026-64274 disclosed?
CVE-2026-64274 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64274 actively exploited?
CVE-2026-64274 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-64274?
CVE-2026-64274 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64274?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64274, 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-64274

Explore →

Is Your Infrastructure Affected by CVE-2026-64274?

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