CVE-2026-80569

published 26 Aug 2026 · updated 19 Nov 2026

Input: synaptics-rmi4 - bound the F54 report size to the allocated buffer

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel b7b9a8b1c303b62371698e396654d6724c79cb74, Kernel 12be3c6ca9589afd6ade41a59c761866e526634d, Kernel 42eaf0e6f79c487f419737314cf0760f7331d368 and 12 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=c762cc68b6a12eedebefc156ea4838e54804e2eb <b7b9a8b1c303b62371698e396654d6724c79cb74, >=c762cc68b6a12eedebefc156ea4838e54804e2eb <12be3c6ca9589afd6ade41a59c761866e526634d, >=c762cc68b6a12eedebefc156ea4838e54804e2eb <42eaf0e6f79c487f419737314cf0760f7331d368, >=c762cc68b6a12eedebefc156ea4838e54804e2eb <49c5adc2b7d6e43c5cf033e1c86fdb9c16ababb1, >=c762cc68b6a12eedebefc156ea4838e54804e2eb <6b06aab79ff166d5781ce792d91acc2e58b1770b, >=c762cc68b6a12eedebefc156ea4838e54804e2eb <6b3bdd44d4cd7d5e35de1d0f06d4930f3cecd403, >=c762cc68b6a12eedebefc156ea4838e54804e2eb <b2f596f00d27703ce09167201ba57f55be8d2f9a, >=c762cc68b6a12eedebefc156ea4838e54804e2eb <b3932101c9c457148038392bc977f9b31e125a86, =4.10b7b9a8b1c303b62371698e396654d6724c79cb74, 12be3c6ca9589afd6ade41a59c761866e526634d, 42eaf0e6f79c487f419737314cf0760f7331d368, 49c5adc2b7d6e43c5cf033e1c86fdb9c16ababb1, 6b06aab79ff166d5781ce792d91acc2e58b1770b, 6b3bdd44d4cd7d5e35de1d0f06d4930f3cecd403, b2f596f00d27703ce09167201ba57f55be8d2f9a, b3932101c9c457148038392bc977f9b31e125a86
linux-kernel: Kernel>=5.11.0 <5.15.217, >=5.16.0 <6.1.184, >=6.13.0 <6.18.46, >=6.19.0 <7.1.10, >=6.2.0 <6.6.153, >=6.7.0 <6.12.105, >=4.10.0 <5.10.2665.15.217, 6.1.184, 6.18.46, 7.1.10, 6.6.153, 6.12.105, 5.10.266

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-80569 severity on Zeptric[![CVE-2026-80569](https://zeptric.io/badge/cve/CVE-2026-80569.svg)](https://zeptric.io/cve/CVE-2026-80569)