CVE-2026-64274

Input: goodix - clamp the device-reported contact count

HIGH
7.8
CVSS Score
Published: July 25, 2026 at 08:49 AM UTC
Updated: October 24, 2026 at 01:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.1 ≤ v < 5.10.2615.11 ≤ v < 5.15.2125.16 ≤ v < 6.1.1786.13 ≤ v < 6.18.396.19 ≤ v < 7.1.46.2 ≤ v < 6.6.1456.7 ≤ v < 6.12.964.1a7ac7c95d4682883d141c5d7a7544d2818f0a09f
Vendor states this is fixed in 2a67668690129953e898923260a2dd1c7c196495 (fixed)
Vendor states this is fixed in 3b32303460155603d25444274856013d211d5e1f (fixed)
Vendor states this is fixed in 46addbd13dbf4aacb71cfbca964a5e552d0f45ae (fixed)
Vendor states this is fixed in 4bfea9c3a0981c1c7fc5d1a1b27197b2de247902 (fixed)
Vendor states this is fixed in 5ed62a96e06be4e94b8296b7932afee550a70e04 (fixed)
Vendor states this is fixed in 719d1a2c83a46be6bf81af905e4f6adb3d32dc28 (fixed)
Vendor states this is fixed in 98b2caef249183b572c04451365246f919707845 (fixed)
Vendor states this is fixed in e825f352ef5271255cd08cc994b0dc25648a2f38 (fixed)
Vendor states this is fixed in 4.1 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.4 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card