CVE-2026-64274
CVE CVE-2026-64274EUVD EUVD-2026-48986Published 2026-07-25T08:49:20.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.12.96; patch: 5.15.212; a7ac7c95d4682883d141c5d7a7544d2818f0a09f <719d1a2c83a46be6bf81af905e4f6adb3d32dc28; a7ac7c95d4682883d141c5d7a7544d2818f0a09f <3b32303460155603d25444274856013d211d5e1f; a7ac7c95d4682883d141c5d7a7544d2818f0a09f <5ed62a96e06be4e94b8296b7932afee550a70e04; a7ac7c95d4682883d141c5d7a7544d2818f0a09f <e825f352ef5271255cd08cc994b0dc25648a2f38; patch: 5.10.261; patch: 6.1.178; a7ac7c95d4682883d141c5d7a7544d2818f0a09f <98b2caef249183b572c04451365246f919707845; a7ac7c95d4682883d141c5d7a7544d2818f0a09f <2a67668690129953e898923260a2dd1c7c196495; patch: 6.18.39; patch: 7.2-rc1; patch: 7.1.4; a7ac7c95d4682883d141c5d7a7544d2818f0a09f <4bfea9c3a0981c1c7fc5d1a1b27197b2de247902; a7ac7c95d4682883d141c5d7a7544d2818f0a09f <46addbd13dbf4aacb71cfbca964a5e552d0f45ae; patch: 0; patch: 6.6.145; 4.1
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.