# CVE-2026-80573: Input: iforce - validate input packet lengths

> A missing length validation in the Linux kernel iforce driver allows local attackers to cause a denial of service via malformed USB input packets.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** AZL-97707, BELL-CVE-2026-80573, DEBIAN-CVE-2026-80573, GHSA-2cc7-72rv-6m2m, UBUNTU-CVE-2026-80573

## What is CVE-2026-80573?

CVE-2026-80573 is a denial of service vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-80573?


## How do I fix CVE-2026-80573?

Apply the vendor's patch.

## Is CVE-2026-80573 being exploited?

There is no known exploitation of CVE-2026-80573 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80573 and fix it if it is affected.

What it is: CVE-2026-80573 is a denial of service vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80573 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80573/ (Markdown: https://insights.sbomify.com/CVE-2026-80573/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80573
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80573
- OSV: https://osv.dev/vulnerability/CVE-2026-80573

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80573/
Summaries are generated and may contain mistakes; the official description above is the record.