Linux Kernel up to 6.6.152/6.12.104/6.18.45/7.1.9 hynitron_cstxxx cst3xx_report_contact memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.8$0-$5k0.30+

Summaryinfo

A vulnerability identified as problematic has been detected in Linux Kernel up to 6.6.152/6.12.104/6.18.45/7.1.9. This affects the function cst3xx_report_contact of the component hynitron_cstxxx. Performing a manipulation results in memory corruption. This vulnerability is cataloged as CVE-2026-80566. The attack must be initiated from a local position. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 6.6.152/6.12.104/6.18.45/7.1.9. This affects the function cst3xx_report_contact of the component hynitron_cstxxx. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-80566 since 08/26/2026. The exploitability is told to be easy. Attacking locally is a requirement. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/26/2026).

Upgrading to version 6.6.153, 6.12.105, 6.18.46 or 7.1.10 eliminates this vulnerability. Applying the patch ec61ca4e310665816a639cb2e46cd9b3af0a9bee/387829ee60de26c7c073ed4e27ecfab2b75d4c74/38e7d5c1ade04b99c70da0298ca296ee62bc99c0/51c5503554c87e4de4035468bebf186205391ce9/27f380ef0e1d3de3cde114e02d33f9320ce3a5a6 is able to eliminate this problem.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.9
VulDB Meta Temp Score: 3.8

VulDB Base Score: 3.9
VulDB Temp Score: 3.8
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.153/6.12.105/6.18.46/7.1.10
Patch: ec61ca4e310665816a639cb2e46cd9b3af0a9bee/387829ee60de26c7c073ed4e27ecfab2b75d4c74/38e7d5c1ade04b99c70da0298ca296ee62bc99c0/51c5503554c87e4de4035468bebf186205391ce9/27f380ef0e1d3de3cde114e02d33f9320ce3a5a6

Timelineinfo

08/26/2026 Advisory disclosed
08/26/2026 +0 days CVE reserved
08/26/2026 +0 days VulDB entry created
08/26/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-80566 (🔒)
GCVE (CVE): GCVE-0-2026-80566
GCVE (VulDB): GCVE-100-395859

Entryinfo

Created: 08/26/2026 17:48
Changes: 08/26/2026 17:48 (59)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!