Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 0ec411167655ef3ff3e84f6af685e962aff9a75b
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 609be40988898a4d75225ade0ea5c1734757dd33
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < e73d7a7d913d89141321f5f3f16343ecc200d152
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5232529eaf57f08fe37484e301579a1915b93d14
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2c083ab16e33fbff3ab8c752fbf8118ed3dd31ce
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a64a8b6b31cd669f0449138e53cc2592d454ccf1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 84e5cb517f445dadbd5f8bf4ec513540e51f9c36
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5751c781d3c97ab6ce0e2a966156ed882152c415
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 5.10.266 – ≤ 5.10.*
    • unaffected 5.15.217 – ≤ 5.15.*
    • unaffected 6.1.184 – ≤ 6.1.*
    • unaffected 6.6.153 – ≤ 6.6.*
    • unaffected 6.12.105 – ≤ 6.12.*
    • unaffected 6.18.46 – ≤ 6.18.*
    • unaffected 7.1.10 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80573 badge
[![CVE-2026-80573](https://cveledger.app/badge/CVE-2026-80573.svg)](https://cveledger.app/cve/CVE-2026-80573)

Record last updated .