Kernel memory corruption via oversized F54 report
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 V4L2 capture. rmi_f54_get_report_size() uses F55 electrode counts to size reads into report_data, which was allocated from smaller F54 counts, so rmi_f54_work() writes past the heap buffer. Exploitation requires access to the F54 diagnostics video node and a malicious or malfunctioning RMI4 device; successful triggering can disclose or corrupt kernel memory and panic the host.
Summary
What happened
Heap buffer overflow in the synaptics-rmi4 F54 driver in Linux allows local users to corrupt kernel memory through V4L2 capture. rmi_f54_get_report_size() uses F55 electrode counts to size reads into report_data, which was allocated from smaller F54 counts, so rmi_f54_work() writes past the heap buffer. Exploitation requires access to the F54 diagnostics video node and a malicious or malfunctioning RMI4 device; successful triggering can disclose or corrupt kernel memory and panic the host.
The record
- CVE
- CVE-2026-80569
- Published
- Aug 26, 2026
- Updated
- Aug 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-120, 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=4.10
- Affected versionversion=c762cc68b6a12eedebefc156ea4838e54804e2eb <12be3c6ca9589afd6ade41a59c761866e526634d
- Affected versionversion=c762cc68b6a12eedebefc156ea4838e54804e2eb <42eaf0e6f79c487f419737314cf0760f7331d368
- Affected versionversion=c762cc68b6a12eedebefc156ea4838e54804e2eb <49c5adc2b7d6e43c5cf033e1c86fdb9c16ababb1
- Affected versionversion=c762cc68b6a12eedebefc156ea4838e54804e2eb <6b06aab79ff166d5781ce792d91acc2e58b1770b
- Affected versionversion=c762cc68b6a12eedebefc156ea4838e54804e2eb <6b3bdd44d4cd7d5e35de1d0f06d4930f3cecd403
- Affected versionversion=c762cc68b6a12eedebefc156ea4838e54804e2eb <b2f596f00d27703ce09167201ba57f55be8d2f9a
- Affected versionversion=c762cc68b6a12eedebefc156ea4838e54804e2eb <b3932101c9c457148038392bc977f9b31e125a86
- Affected versionversion=c762cc68b6a12eedebefc156ea4838e54804e2eb <b7b9a8b1c303b62371698e396654d6724c79cb74
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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