CVE-2026-80570

Input: synaptics-rmi4 - zero report size on F54 work error

HIGH
7.8
CVSS Score
Published: August 26, 2026 at 02:37 PM UTC
Updated: August 27, 2026 at 06:30 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - zero report size on F54 work error In rmi_f54_work(), if an error occurs during report request or command verification, the code jumped directly to the 'error' label, bypassing the 'abort' label where f54->report_size was normally zeroed out. This left f54->report_size containing its previous successful payload size. If a user then altered the V4L2 format to a smaller size, and a subsequent run failed, rmi_f54_buffer_queue() would copy the stale, larger payload size into the shrunken V4L2 buffer, causing a heap buffer overflow. Fix this by merging the 'abort' and 'error' labels into a single 'out' exit path, and ensuring that f54->report_size is always set to 0 on failure by checking for error and zeroing the local report_size first.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.9 ≤ v < 5.10.2664.9 ≤ v < 5.15.2174.9 ≤ v < 6.1.1844.9 ≤ v < 6.12.1054.9 ≤ v < 6.18.464.9 ≤ v < 6.6.1534.9 ≤ v < 7.1.104.9 ≤ v < 7.23a762dbd5347514c3cb2ac756a92a3d1c7646a2d4.9
Vendor states this is fixed in 62079c17ec07d64362bec367ee7a525b0dbf6bf9 (fixed)
Vendor states this is fixed in 77749685e55da19b187df215b5da4080842ca5c7 (fixed)
Vendor states this is fixed in 79521ed3cc9ea48476666ccacf45ecd6954b29a4 (fixed)
Vendor states this is fixed in 88c8174d72900d77fbdf2f527d54b6ff2da876a8 (fixed)
Vendor states this is fixed in b28593a05afdd812b590e1045b5bd862a5869225 (fixed)
Vendor states this is fixed in c669c64ab71afa7b467c4d7e18f6a05e96b97a1f (fixed)
Vendor states this is fixed in c6cfda79f26c69e97db9805808c3b44d02227b4b (fixed)
Vendor states this is fixed in dc76c3c8e8ad09362b8c1561f3928288c15cba2e (fixed)
Vendor states this is fixed in 4.9 (unaffected)
Vendor states this is fixed in 5.10.266 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.105 (unaffected)
Vendor states this is fixed in 6.18.46 (unaffected)
Vendor states this is fixed in 6.6.153 (unaffected)
Vendor states this is fixed in 7.1.10 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card