CVE-2026-80566

Input: hynitron_cstxxx - validate touch count and finger IDs

N/A
Published: August 26, 2026 at 02:37 PM UTC
Updated: August 26, 2026 at 03:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.2 ≤ v < 6.12.1056.2 ≤ v < 6.18.466.2 ≤ v < 6.6.1536.2 ≤ v < 7.1.106.2 ≤ v < 7.26.266603243f5283f7f28c795f09e7c2167233df0bd
Vendor states this is fixed in 27f380ef0e1d3de3cde114e02d33f9320ce3a5a6 (fixed)
Vendor states this is fixed in 387829ee60de26c7c073ed4e27ecfab2b75d4c74 (fixed)
Vendor states this is fixed in 38e7d5c1ade04b99c70da0298ca296ee62bc99c0 (fixed)
Vendor states this is fixed in 51c5503554c87e4de4035468bebf186205391ce9 (fixed)
Vendor states this is fixed in ec61ca4e310665816a639cb2e46cd9b3af0a9bee (fixed)
Vendor states this is fixed in 6.12.105 (unaffected)
Vendor states this is fixed in 6.18.46 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)
Vendor states this is fixed in 6.6.153 (unaffected)
Vendor states this is fixed in 7.1.10 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card