CVE-2026-80570
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Record status
- Received
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-80570.md and follow it. Check whether this project is affected by CVE-2026-80570. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- https://git.kernel.org/stable/c/62079c17ec07d64362bec367ee7a525b0dbf6bf9
- https://git.kernel.org/stable/c/77749685e55da19b187df215b5da4080842ca5c7
- https://git.kernel.org/stable/c/79521ed3cc9ea48476666ccacf45ecd6954b29a4
- https://git.kernel.org/stable/c/88c8174d72900d77fbdf2f527d54b6ff2da876a8
- https://git.kernel.org/stable/c/b28593a05afdd812b590e1045b5bd862a5869225
- https://git.kernel.org/stable/c/c669c64ab71afa7b467c4d7e18f6a05e96b97a1f
- https://git.kernel.org/stable/c/c6cfda79f26c69e97db9805808c3b44d02227b4b
- https://git.kernel.org/stable/c/dc76c3c8e8ad09362b8c1561f3928288c15cba2e