Kernel crash via signed loop-counter overflow
Published Aug 28, 2026 · Updated Aug 28, 2026
NULL pointer dereference in the Linux kernel HID picoLCD driver allows attackers to crash the kernel through an excessive loop count. In picolcd_send_and_wait(), signed counter k wraps after more than INT_MAX report-field iterations, so k < size becomes true at size zero and dereferences raw_data despite its NULL value. The public record does not establish a practical way to force that iteration count; the documented consequence is a theoretical kernel crash.
Summary
What happened
NULL pointer dereference in the Linux kernel HID picoLCD driver allows attackers to crash the kernel through an excessive loop count. In picolcd_send_and_wait(), signed counter k wraps after more than INT_MAX report-field iterations, so k < size becomes true at size zero and dereferences raw_data despite its NULL value. The public record does not establish a practical way to force that iteration count; the documented consequence is a theoretical kernel crash.
The record
- CVE
- CVE-2026-80605
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.7
- Affected versionversion=fabdbf2fd22fa170b4c5340dbdda5c8cd88fb205 <0021eb09041f021c079be1022934a280f7f176c0
- Affected versionversion=fabdbf2fd22fa170b4c5340dbdda5c8cd88fb205 <42dc0b7b55fe0499fc09183f34a1c46d1dcccf77
- Affected versionversion=fabdbf2fd22fa170b4c5340dbdda5c8cd88fb205 <48caee2c106b03301c72fe389ebff00d852c58d5
- Affected versionversion=fabdbf2fd22fa170b4c5340dbdda5c8cd88fb205 <a02d5d7ad7ae5fa3756b8332f7350e973085dcb3
- Affected versionversion=fabdbf2fd22fa170b4c5340dbdda5c8cd88fb205 <d354e523c6f740db758cafcd4c11bb7913285ed8
- Affected versionversion=fabdbf2fd22fa170b4c5340dbdda5c8cd88fb205 <dc176447c7279435c46735db7da81aed1ec25cc2
- Affected versionversion=fabdbf2fd22fa170b4c5340dbdda5c8cd88fb205 <e4edeefb8d5bfceb2058e2b3291f4ae1e5a76e61
- Affected versionversion=fabdbf2fd22fa170b4c5340dbdda5c8cd88fb205 <ef649703dce0df1364fcec3cdad9b32d1c522939
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo