Bug 2524499 (CVE-2026-80570)

Summary: CVE-2026-80570 kernel: Input: synaptics-rmi4 - zero report size on F54 work error
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: rhel-process-autobot, watson-tool-maintainers
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the `synaptics-rmi4` component of the Linux kernel. This vulnerability occurs when an error in processing a report request or command leads to an incorrect size being used for subsequent data operations. A local user could exploit this by manipulating the video format, causing the system to attempt to write a larger amount of data than allocated. This results in a heap buffer overflow, which could lead to a system crash (Denial of Service) or potentially allow an attacker to execute unauthorized code.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-08-26 15:02:24 UTC 
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.
Comment 1 gkamathe 2026-08-27 13:22:17 UTC 
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026082612-CVE-2026-80570-2cb3@gregkh/T