Local memory corruption via stale F54 report size
Published Aug 26, 2026 · Updated Aug 27, 2026
Heap buffer overflow in the synaptics-rmi4 F54 driver in Linux allows local users to corrupt kernel memory through the V4L2 interface. On an F54 work error, rmi_f54_work retains the prior report size, so rmi_f54_buffer_queue copies that stale length into a smaller buffer. Access to local V4L2 ioctls and an F54 diagnostics node is required; triggering the overflow can crash the system or alter kernel memory.
Summary
What happened
Heap buffer overflow in the synaptics-rmi4 F54 driver in Linux allows local users to corrupt kernel memory through the V4L2 interface. On an F54 work error, rmi_f54_work retains the prior report size, so rmi_f54_buffer_queue copies that stale length into a smaller buffer. Access to local V4L2 ioctls and an F54 diagnostics node is required; triggering the overflow can crash the system or alter kernel memory.
The record
- CVE
- CVE-2026-80570
- Published
- Aug 26, 2026
- Updated
- Aug 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-805, CWE-122, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 26, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3a762dbd5347514c3cb2ac756a92a3d1c7646a2d <62079c17ec07d64362bec367ee7a525b0dbf6bf9
- Affected versionversion=3a762dbd5347514c3cb2ac756a92a3d1c7646a2d <77749685e55da19b187df215b5da4080842ca5c7
- Affected versionversion=3a762dbd5347514c3cb2ac756a92a3d1c7646a2d <79521ed3cc9ea48476666ccacf45ecd6954b29a4
- Affected versionversion=3a762dbd5347514c3cb2ac756a92a3d1c7646a2d <88c8174d72900d77fbdf2f527d54b6ff2da876a8
- Affected versionversion=3a762dbd5347514c3cb2ac756a92a3d1c7646a2d <b28593a05afdd812b590e1045b5bd862a5869225
- Affected versionversion=3a762dbd5347514c3cb2ac756a92a3d1c7646a2d <c669c64ab71afa7b467c4d7e18f6a05e96b97a1f
- Affected versionversion=3a762dbd5347514c3cb2ac756a92a3d1c7646a2d <c6cfda79f26c69e97db9805808c3b44d02227b4b
- Affected versionversion=3a762dbd5347514c3cb2ac756a92a3d1c7646a2d <dc76c3c8e8ad09362b8c1561f3928288c15cba2e
- Affected versionversion=4.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo