CVE-2026-80573 — Input: iforce - validate input packet lengths
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 0ec411167655ef3ff3e84f6af685e962aff9a75b≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 609be40988898a4d75225ade0ea5c1734757dd33≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < e73d7a7d913d89141321f5f3f16343ecc200d152≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 5232529eaf57f08fe37484e301579a1915b93d14≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 2c083ab16e33fbff3ab8c752fbf8118ed3dd31ce≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < a64a8b6b31cd669f0449138e53cc2592d454ccf1≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 84e5cb517f445dadbd5f8bf4ec513540e51f9c36≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 5751c781d3c97ab6ce0e2a966156ed882152c415 and 1 moreversion 2.6.12 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 27, 2026 · 12 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/5751c781d3c97ab6ce0e2a966156ed882152c415
- git.kernel.org/stable/c/a64a8b6b31cd669f0449138e53cc2592d454ccf1
- git.kernel.org/stable/c/609be40988898a4d75225ade0ea5c1734757dd33
- git.kernel.org/stable/c/5232529eaf57f08fe37484e301579a1915b93d14
- git.kernel.org/stable/c/0ec411167655ef3ff3e84f6af685e962aff9a75b
- git.kernel.org/stable/c/2c083ab16e33fbff3ab8c752fbf8118ed3dd31ce
- git.kernel.org/stable/c/e73d7a7d913d89141321f5f3f16343ecc200d152
- git.kernel.org/stable/c/84e5cb517f445dadbd5f8bf4ec513540e51f9c36
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 5h
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 5h
- Unknown CVE-2026-99214 drm/vc4: hdmi: Move packet RAM enable to PM runtime 5h
- Unknown CVE-2026-99213 vsock: treat TCP_CLOSING as once-established 5h
- Unknown CVE-2026-99212 net/rds: don't let the rdma_cm destroy an id RDS still owns on route failure 5h
- Unknown CVE-2026-99211 netlink: reset skb headers before unicast and multicast filtering 5h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-80573 is "Input: iforce - validate input packet lengths", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.