Memory corruption via oversized USB serial write
Published Jun 25, 2026 · Updated Jun 25, 2026
Out-of-bounds write in the kl5kusb105 USB serial driver in Linux Kernel allows local users to corrupt kernel memory through TTY writes. klsi_105_prepare_write_buffer reserves a two-byte header but copies up to the full 64-byte buffer size at a two-byte offset, overwriting the slab allocation. The driver must be present and its TTY must receive at least 64 bytes; the overwrite extends two bytes beyond the allocated buffer.
Summary
What happened
Out-of-bounds write in the kl5kusb105 USB serial driver in Linux Kernel allows local users to corrupt kernel memory through TTY writes. klsi_105_prepare_write_buffer reserves a two-byte header but copies up to the full 64-byte buffer size at a two-byte offset, overwriting the slab allocation. The driver must be present and its TTY must receive at least 64 bytes; the overwrite extends two bytes beyond the allocated buffer.
The record
- CVE
- CVE-2026-53194
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 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=2.6.35
- Affected versionversion=60b3013cdaf3fa8a17243ca46b19db3cbe08d943 <0a57320f71941d4e0b1307453c9a1f0939afe666
- Affected versionversion=60b3013cdaf3fa8a17243ca46b19db3cbe08d943 <14147b7963685957839c76ba8094924e22777d79
- Affected versionversion=60b3013cdaf3fa8a17243ca46b19db3cbe08d943 <372f33ebed747d91870f57c0a2e62884a870bffa
- Affected versionversion=60b3013cdaf3fa8a17243ca46b19db3cbe08d943 <60af1fd82983c26604102e63a3fcc822c186cceb
- Affected versionversion=60b3013cdaf3fa8a17243ca46b19db3cbe08d943 <70d86e355c564b5510fde61361df014f5476c83e
- Affected versionversion=60b3013cdaf3fa8a17243ca46b19db3cbe08d943 <96d47e40bf9db4a9efd5c8fb53287a508d165f14
- Affected versionversion=60b3013cdaf3fa8a17243ca46b19db3cbe08d943 <a1288cd700f721c1a119c4f1e8efa234e59caada
- Affected versionversion=60b3013cdaf3fa8a17243ca46b19db3cbe08d943 <bde742b076cbe26ecc89c8c68c76ae076a524d02
What conditions does exploitation require?
What is affected?
Published CVSS scores
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