SECUFOCUSNOW
Home›CVE index›CVE-2026-80570
ReviewHigh

CVE-2026-80570

Linux

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, cau...

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2026.08.27
PRIORITY ASSESSMENT

Review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

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, cau...

Affected product and versions

Product
Linux
Affected versions
>= 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d < 62079c17ec07d64362bec367ee7a525b0dbf6bf9, >= 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d < 79521ed3cc9ea48476666ccacf45ecd6954b29a4, >= 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d < c669c64ab71afa7b467c4d7e18f6a05e96b97a1f, >= 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d < 77749685e55da19b187df215b5da4080842ca5c7, >= 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d < c6cfda79f26c69e97db9805808c3b44d02227b4b, >= 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d < b28593a05afdd812b590e1045b5bd862a5869225, >= 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d < 88c8174d72900d77fbdf2f527d54b6ff2da876a8, >= 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d < dc76c3c8e8ad09362b8c1561f3928288c15cba2e, >= 4.9
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available