CVE-2026-80573: Input: iforce - validate input packet lengths
Noroxi assessment
Priority: Monitor (action score 0/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.22% (FIRST EPSS).
- Fixed version: Linux Linux 0ec411167655ef3ff3e84f6af685e962aff9a75b, 2c083ab16e33fbff3ab8c752fbf8118ed3dd31ce, 5232529eaf57f08fe37484e301579a1915b93d14; 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 0ec411167655ef3ff3e84f6af685e962aff9a75b, 2c083ab16e33fbff3ab8c752fbf8118ed3dd31ce, 5232529eaf57f08fe37484e301579a1915b93d14; 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: 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.
- Published
- Aug 26, 2026
- Updated
- Aug 27, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 0ec411167655ef3ff3e84f6af685e962aff9a75baffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 609be40988898a4d75225ade0ea5c1734757dd33affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before e73d7a7d913d89141321f5f3f16343ecc200d152affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 5232529eaf57f08fe37484e301579a1915b93d14affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 2c083ab16e33fbff3ab8c752fbf8118ed3dd31ceaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before a64a8b6b31cd669f0449138e53cc2592d454ccf1affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 84e5cb517f445dadbd5f8bf4ec513540e51f9c36affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 5751c781d3c97ab6ce0e2a966156ed882152c415affected · git
- before 2.6.12not 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-80570Aug 26, 2026 · Input: synaptics-rmi4 - zero report size on F54 work error31Monitor
- ← EarlierCVE-2026-80571Aug 26, 2026 · powerpc/pseries: papr-phy-attest - validate cmd.length, plug mem leak0Monitor
- Later →CVE-2026-80575Aug 26, 2026 · Input: cs40l50-vibra - validate custom data from user space31Monitor
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 | 0ec411167655ef3ff3e84f6af685e962aff9a75b | Vendor (CNA) |
| Linux Linux | 2c083ab16e33fbff3ab8c752fbf8118ed3dd31ce | Vendor (CNA) |
| Linux Linux | 5232529eaf57f08fe37484e301579a1915b93d14 | Vendor (CNA) |
| Linux Linux | 5751c781d3c97ab6ce0e2a966156ed882152c415 | Vendor (CNA) |
| Linux Linux | 609be40988898a4d75225ade0ea5c1734757dd33 | Vendor (CNA) |
| Linux Linux | 84e5cb517f445dadbd5f8bf4ec513540e51f9c36 | Vendor (CNA) |
| Linux Linux | a64a8b6b31cd669f0449138e53cc2592d454ccf1 | Vendor (CNA) |
| Linux Linux | e73d7a7d913d89141321f5f3f16343ecc200d152 | 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).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2c083ab16e33fbff3ab8c752fbf8118ed3dd31ce
- git.kernel.org/stable/c/5232529eaf57f08fe37484e301579a1915b93d14
- git.kernel.org/stable/c/5751c781d3c97ab6ce0e2a966156ed882152c415
- git.kernel.org/stable/c/609be40988898a4d75225ade0ea5c1734757dd33
- git.kernel.org/stable/c/84e5cb517f445dadbd5f8bf4ec513540e51f9c36
- git.kernel.org/stable/c/a64a8b6b31cd669f0449138e53cc2592d454ccf1
- git.kernel.org/stable/c/e73d7a7d913d89141321f5f3f16343ecc200d152
Vendor advisories and official records. Exploit/PoC links are deliberately left out.