System crash via unclamped touchscreen contact count
Published Jul 25, 2026 · Updated Jul 25, 2026
An out-of-bounds write in the Linux Kernel Goodix touchscreen driver allows physically proximate attackers to crash systems via I2C. goodix_ts_read_input_report() trusts the controller's four-bit maximum-contact field, accepts as many as 15 contacts, and lets goodix_i2c_read() write up to 45 bytes beyond the 92-byte point_data stack buffer. Exploitation requires a malicious or counterfeit controller or physical access to tamper with the I2C bus; the documented consequence is a kernel crash.
Summary
What happened
An out-of-bounds write in the Linux Kernel Goodix touchscreen driver allows physically proximate attackers to crash systems via I2C. goodix_ts_read_input_report() trusts the controller's four-bit maximum-contact field, accepts as many as 15 contacts, and lets goodix_i2c_read() write up to 45 bytes beyond the 92-byte point_data stack buffer. Exploitation requires a malicious or counterfeit controller or physical access to tamper with the I2C bus; the documented consequence is a kernel crash.
The record
- CVE
- CVE-2026-64274
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-787, T1200
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.1
- Affected versionversion=a7ac7c95d4682883d141c5d7a7544d2818f0a09f <2a67668690129953e898923260a2dd1c7c196495
- Affected versionversion=a7ac7c95d4682883d141c5d7a7544d2818f0a09f <3b32303460155603d25444274856013d211d5e1f
- Affected versionversion=a7ac7c95d4682883d141c5d7a7544d2818f0a09f <46addbd13dbf4aacb71cfbca964a5e552d0f45ae
- Affected versionversion=a7ac7c95d4682883d141c5d7a7544d2818f0a09f <4bfea9c3a0981c1c7fc5d1a1b27197b2de247902
- Affected versionversion=a7ac7c95d4682883d141c5d7a7544d2818f0a09f <5ed62a96e06be4e94b8296b7932afee550a70e04
- Affected versionversion=a7ac7c95d4682883d141c5d7a7544d2818f0a09f <719d1a2c83a46be6bf81af905e4f6adb3d32dc28
- Affected versionversion=a7ac7c95d4682883d141c5d7a7544d2818f0a09f <98b2caef249183b572c04451365246f919707845
- Affected versionversion=a7ac7c95d4682883d141c5d7a7544d2818f0a09f <e825f352ef5271255cd08cc994b0dc25648a2f38
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo