CVE-2026-80569
Input: synaptics-rmi4 - bound the F54 report size to the allocated buffer
Reported by linux · Published August 26, 2026
In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - bound the F54 report size to the allocated buffer rmi_f54_work() reads a diagnostics report from the device into f54->report_data, sizing the transfer with rmi_f54_get_report_size(): report_size = rmi_f54_get_report_size(f54); ... for (i = 0; i < report_size; i += F54_REPORT_DATA_SIZE) { int size = min(F54_REPORT_DATA_SIZE, report_size - i); ... rmi_read_block(.., f54->report_data + i, size); } report_data is allocated once at probe from F54's own electrode counts (array3_size(f54->num_tx_electrodes, f54->num_rx_electrodes, sizeof(u16))), but rmi_f54_get_report_size() computes the size from drv_data->num_*_electrodes when those are set, i.e. from the F55 function's electrode counts. Both counts come straight from device queries (F54 and F55 each report up to 255 electrodes) and nothing constrains the F55 counts to the F54 ones. A malicious or malfunctioning RMI4 device that reports larger F55 electrode counts than its F54 counts makes report_size exceed the allocation, so the read loop writes past report_data (and the V4L2 dequeue memcpy() then reads past it). On conforming hardware the F55 configured electrodes are a subset of the F54 physical electrodes, so report_size never exceeds the buffer and well-behaved devices are unaffected. Record the allocation size and reject a report that does not fit, mirroring the existing zero-size check.
EPSS 0.12% · 1.8th percentile
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | c762cc68b6a12eedebefc156ea4838e54804e2eb, c762cc68b6a12eedebefc156ea4838e54804e2eb, c762cc68b6a12eedebefc156ea4838e54804e2eb |
| Linux | Linux | 4.10, 0, 5.10.266 |
| linux | linux_kernel | 4.10, 4.10, 4.10 |
| Linux | Linux | *, *, * |
Timeline
- Aug 26, 2026 CVE Published
- Aug 27, 2026 EPSS Score (6 in total, the first dated here)
- Aug 27, 2026 CVE Updated
- Sep 2, 2026 Security Advisory
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-80569
vulnetix vdb fixes CVE-2026-80569
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80569/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart