Menu

Star on GitHub · 3.2k

CVE-2026-80573

In the Linux kernel, the following vulnerability has been resolved: Input: iforce - validate input packet lengths iforce_process_packet() reads fixed fields from joystick, wheel and status packet…

Published Aug 26, 2026EPSS 0.22%

Overview

CVE-2026-80573 is a known-severity vulnerability. It was published on August 26, 2026.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

Input: iforce - validate input packet lengths

iforce_process_packet() reads fixed fields from joystick, wheel and

status packets without first checking their lengths. In particular, the

shared hats-and-buttons helper unconditionally reads data[6]. The status

tail is a sequence of 16-bit effect addresses, but an incomplete final

address is also consumed. A successful zero-length USB URB additionally

reads the packet ID before the common parser is called.

Reject the zero-length USB transfer, require the seven-byte joystick and

wheel prefixes and the two-byte status prefix, and consume only complete

status-tail addresses.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-80573?

CVE-2026-80573 is a known-severity vulnerability. It was published on August 26, 2026.

How severe is CVE-2026-80573?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-80573?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-80573?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-80573 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.