CVE-2026-80570: Input: synaptics-rmi4 - zero report size on F54 work error
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 62079c17ec07d64362bec367ee7a525b0dbf6bf9, 77749685e55da19b187df215b5da4080842ca5c7, 79521ed3cc9ea48476666ccacf45ecd6954b29a4; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 62079c17ec07d64362bec367ee7a525b0dbf6bf9, 77749685e55da19b187df215b5da4080842ca5c7, 79521ed3cc9ea48476666ccacf45ecd6954b29a4; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 26, 2026
- Updated
- Aug 27, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.9affected
- 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and later · before 62079c17ec07d64362bec367ee7a525b0dbf6bf9affected · git
- 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and later · before 79521ed3cc9ea48476666ccacf45ecd6954b29a4affected · git
- 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and later · before c669c64ab71afa7b467c4d7e18f6a05e96b97a1faffected · git
- 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and later · before 77749685e55da19b187df215b5da4080842ca5c7affected · git
- 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and later · before c6cfda79f26c69e97db9805808c3b44d02227b4baffected · git
- 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and later · before b28593a05afdd812b590e1045b5bd862a5869225affected · git
- 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and later · before 88c8174d72900d77fbdf2f527d54b6ff2da876a8affected · git
- 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and later · before dc76c3c8e8ad09362b8c1561f3928288c15cba2eaffected · git
- before 4.9not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.10-1 | 7.1.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80568Aug 26, 2026 · Input: synaptics-rmi4 - block s_input when F54 queue is busy31Monitor
- ← EarlierCVE-2026-80569Aug 26, 2026 · Input: synaptics-rmi4 - bound the F54 report size to the allocated buffer31Monitor
- Later →CVE-2026-80571Aug 26, 2026 · powerpc/pseries: papr-phy-attest - validate cmd.length, plug mem leak0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 62079c17ec07d64362bec367ee7a525b0dbf6bf9 | Vendor (CNA) |
| Linux Linux | 77749685e55da19b187df215b5da4080842ca5c7 | Vendor (CNA) |
| Linux Linux | 79521ed3cc9ea48476666ccacf45ecd6954b29a4 | Vendor (CNA) |
| Linux Linux | 88c8174d72900d77fbdf2f527d54b6ff2da876a8 | Vendor (CNA) |
| Linux Linux | b28593a05afdd812b590e1045b5bd862a5869225 | Vendor (CNA) |
| Linux Linux | c669c64ab71afa7b467c4d7e18f6a05e96b97a1f | Vendor (CNA) |
| Linux Linux | c6cfda79f26c69e97db9805808c3b44d02227b4b | Vendor (CNA) |
| Linux Linux | dc76c3c8e8ad09362b8c1561f3928288c15cba2e | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0919 · Aug 27, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/77749685e55da19b187df215b5da4080842ca5c7
- git.kernel.org/stable/c/79521ed3cc9ea48476666ccacf45ecd6954b29a4
- git.kernel.org/stable/c/88c8174d72900d77fbdf2f527d54b6ff2da876a8
- git.kernel.org/stable/c/b28593a05afdd812b590e1045b5bd862a5869225
- git.kernel.org/stable/c/c669c64ab71afa7b467c4d7e18f6a05e96b97a1f
- git.kernel.org/stable/c/c6cfda79f26c69e97db9805808c3b44d02227b4b
- git.kernel.org/stable/c/dc76c3c8e8ad09362b8c1561f3928288c15cba2e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.