Description
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.
Published: 2026-08-26
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A flaw in the Linux kernel synaptics-rmi4 driver allows a malicious or malfunctioning RMI4 device that reports larger F55 electrode counts than its F54 counts to cause a heap buffer overflow when reading diagnostic data. The driver allocates a fixed‑size buffer based on the F54 electrode count but trusts the F55 electrode count to calculate the size of the data it will read. When the device reports an F55 count larger than the allocated buffer, the read loop writes beyond the buffer boundaries, leading to kernel memory corruption that can be exploited to execute arbitrary code with kernel privileges, potentially allowing complete host compromise. The threat that an attacker can control such a device is inferred from the mention of a malicious or malfunctioning device but is not explicitly stated in the advisory.

Affected Systems

The vulnerability is present in any Linux kernel that includes the synaptics‑rmi4 driver in its build, regardless of distribution, as the affected code is part of the core kernel source. No specific kernel version range is provided in the advisory, so all kernels that have not yet received the state‑of‑the‑art patch are potentially affected. Systems that use Synaptics touchpads or other devices that expose an RMI4 interface are at risk whenever the driver is active.

Risk and Exploitability

The CVSS or EPSS scores are not supplied in the advisory. However, because the flaw writes into kernel memory, the potential impact is high. The advisory implies that exploitation requires a malicious RMI4 device that reports anomalous electrode counts. It is inferred that an attacker would need to supply or spoof such a device, which may require physical access or compromised firmware on a connected touchscreen. There is no indication that the flaw is currently demonstrated in the wild, and it is not listed in the CISA KEV catalog. Nonetheless, the high severity of a kernel memory corruption warrants prompt action.

Generated by OpenCVE AI on August 26, 2026 at 16:28 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the kernel to a version that includes the synaptics‑rmi4 patch committed in 2026.
  • If the kernel cannot be updated immediately, unload or block the synaptics‑rmi4 module via modprobe -r or by setting an appropriate disable option in the driver configuration to prevent the vulnerable driver from loading.
  • Where the driver is required, verify that connected RMI4 devices are from trusted vendors and that firmware has not been tampered with; consider implementing device trust checks or enforcements of secure attachment.

Generated by OpenCVE AI on August 26, 2026 at 16:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 26 Aug 2026 16:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-787

Wed, 26 Aug 2026 14:45:00 +0000

Type Values Removed Values Added
Description 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.
Title Input: synaptics-rmi4 - bound the F54 report size to the allocated buffer
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-26T14:37:31.338Z

Reserved: 2026-08-26T14:34:25.768Z

Link: CVE-2026-80569

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-26T15:17:12.457

Modified: 2026-08-26T15:17:12.457

Link: CVE-2026-80569

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-26T16:30:09Z

Weaknesses