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-80566Input: hynitron_cstxxx - validate touch count and finger IDs

Description

In the Linux kernel, the following vulnerability has been resolved: Input: hynitron_cstxxx - validate touch count and finger IDs The driver allocates max_touch_num input slots, which are indexed from zero through max_touch_num - 1. The current check allows a finger ID equal to max_touch_num to reach cst3xx_report_contact(). While the input core ignores out-of-range slot indices, reporting touch data without a valid slot change corrupts the touch state of the previously active slot. The touch count is read from the controller's report and is used to index the fixed-size report buffer without first checking its range. Reject counts larger than the supported number of touch slots before checking the trailing byte or parsing touch data. Reject finger IDs equal to or greater than max_touch_num, and return immediately when an invalid finger ID is encountered so that corrupt touch frames are discarded instead of reporting partial contact state. The V821 Avaota F1 board configures the vendor driver with one touch slot, so finger ID 1 is already invalid on that device.

Timeline

  1. ID reserved

    By Linux

  2. Published

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.16% · top 95% of all CVEs (18 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 66603243f5283f7f28c795f09e7c2167233df0bd – < ec61ca4e310665816a639cb2e46cd9b3af0a9bee
    • affected 66603243f5283f7f28c795f09e7c2167233df0bd – < 387829ee60de26c7c073ed4e27ecfab2b75d4c74
    • affected 66603243f5283f7f28c795f09e7c2167233df0bd – < 38e7d5c1ade04b99c70da0298ca296ee62bc99c0
    • affected 66603243f5283f7f28c795f09e7c2167233df0bd – < 51c5503554c87e4de4035468bebf186205391ce9
    • affected 66603243f5283f7f28c795f09e7c2167233df0bd – < 27f380ef0e1d3de3cde114e02d33f9320ce3a5a6
  • Linux · Linux

    • affected 6.2
    • unaffected < 6.2
    • 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

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .