Vulnerability · Published Jul 25, 2026 · Assigned by Linux
CVE-2026-64274Input: goodix - clamp the device-reported contact count
High 7.8
In plain English
A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 6% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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 packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.180-1 | DEBIAN-CVE-2026-64274 |
| Debian:13 | linux | 6.12.96-1 | DEBIAN-CVE-2026-64274 |
| Debian:14 | linux | 7.1.4-1 | DEBIAN-CVE-2026-64274 |
| Debian:12 | linux-6.12 | 6.12.100-1~deb12u1 | DEBIAN-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux | 5.15.0-198.208 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux | 6.8.0-147.147 | UBUNTU-CVE-2026-64274 |
| Ubuntu:26.04:LTS | linux | 7.0.0-31.31 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1117.124 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1067.70 | UBUNTU-CVE-2026-64274 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1012.12 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-aws-7.0 | 7.0.0-1012.12~24.04.1 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1123.132 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1071.79 | UBUNTU-CVE-2026-64274 |
| Ubuntu:26.04:LTS | linux-azure | 7.0.0-1014.14 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-azure-7.0 | 7.0.0-1014.14~24.04.1 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1122.131 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1069.76 | UBUNTU-CVE-2026-64274 |
| Ubuntu:26.04:LTS | linux-azure-fde | 7.0.0-1013.13 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.17 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1013.13~24.04.1 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1118.128 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1071.79 | UBUNTU-CVE-2026-64274 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1011.11 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-gcp-7.0 | 7.0.0-1011.11~24.04.1 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1113.119 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1066.74 | UBUNTU-CVE-2026-64274 |
| Ubuntu:26.04:LTS | linux-gke | 7.0.0-1006.7 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1100.108 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1052.56 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-31.31~24.04.1 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1111.115 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1067.68 | UBUNTU-CVE-2026-64274 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1013.13 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1112.118 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1109.114 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-195.205 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-147.147.1 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1112.113 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:26.04:LTS | linux-nvidia | 7.0.0-1018.18 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-nvidia-7.0 | 7.0.0-1018.18~24.04.1 | UBUNTU-CVE-2026-64274 |
| Ubuntu:26.04:LTS | linux-nvidia-bos | 7.0.0-2018.18 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1070.72 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1036.39 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1059.59 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:26.04:LTS | linux-oem-7.0 | 7.0.0-1013.13 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1114.120 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1064.67 | UBUNTU-CVE-2026-64274 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1011.11 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-oracle-7.0 | 7.0.0-1011.11~24.04.1 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:26.04:LTS | linux-raspi | 7.0.0-1019.19 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:26.04:LTS | linux-realtime | 7.0.0-31.31.1 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:26.04:LTS | linux-riscv | 7.0.0-31.31.1 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-riscv-7.0 | 7.0.0-31.31.1~24.04.1 | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-vmware | 6.8.0-1008.8 | UBUNTU-CVE-2026-64274 |
| Ubuntu:24.04:LTS | linux-xilinx | no fix listed | UBUNTU-CVE-2026-64274 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1080.84 | UBUNTU-CVE-2026-64274 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | a7ac7c95d4682883d141c5d7a7544d2818f0a09f – before e825f352ef5271255cd08cc994b0dc25648a2f38a7ac7c95d4682883d141c5d7a7544d2818f0a09f – before 4bfea9c3a0981c1c7fc5d1a1b27197b2de247902a7ac7c95d4682883d141c5d7a7544d2818f0a09f – before 98b2caef249183b572c04451365246f919707845a7ac7c95d4682883d141c5d7a7544d2818f0a09f – before 719d1a2c83a46be6bf81af905e4f6adb3d32dc28a7ac7c95d4682883d141c5d7a7544d2818f0a09f – before 46addbd13dbf4aacb71cfbca964a5e552d0f45aea7ac7c95d4682883d141c5d7a7544d2818f0a09f – before 3b32303460155603d25444274856013d211d5e1fa7ac7c95d4682883d141c5d7a7544d2818f0a09f – before 2a67668690129953e898923260a2dd1c7c196495a7ac7c95d4682883d141c5d7a7544d2818f0a09f – before 5ed62a96e06be4e94b8296b7932afee550a70e04 |
| Linux | Linux | 4.1 |
References
- https://git.kernel.org/stable/c/e825f352ef5271255cd08cc994b0dc25648a2f38
- https://git.kernel.org/stable/c/4bfea9c3a0981c1c7fc5d1a1b27197b2de247902
- https://git.kernel.org/stable/c/98b2caef249183b572c04451365246f919707845
- https://git.kernel.org/stable/c/719d1a2c83a46be6bf81af905e4f6adb3d32dc28
- https://git.kernel.org/stable/c/46addbd13dbf4aacb71cfbca964a5e552d0f45ae
- https://git.kernel.org/stable/c/3b32303460155603d25444274856013d211d5e1f
- https://git.kernel.org/stable/c/2a67668690129953e898923260a2dd1c7c196495
- https://git.kernel.org/stable/c/5ed62a96e06be4e94b8296b7932afee550a70e04