Local invalid read via stale USB interface logging
Published Jul 25, 2026 · Updated Jul 25, 2026
Use-after-free in the Linux Kernel chaoskey USB driver allows local users to trigger an invalid read by closing an unplugged device. chaoskey_release calls chaoskey_free, then a debug statement dereferences the released usb_interface pointer in dev_driver_string. Triggering requires an open chaoskey device followed by physical disconnection; the published evidence demonstrates an eight-byte invalid read under KASAN but no broader consequence.
Summary
What happened
Use-after-free in the Linux Kernel chaoskey USB driver allows local users to trigger an invalid read by closing an unplugged device. chaoskey_release calls chaoskey_free, then a debug statement dereferences the released usb_interface pointer in dev_driver_string. Triggering requires an open chaoskey device followed by physical disconnection; the published evidence demonstrates an eight-byte invalid read under KASAN but no broader consequence.
The record
- CVE
- CVE-2026-64455
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 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=4.1
- Affected versionversion=66e3e591891da9899a8990792da080432531ffd4 <2a52d55c86a429dac47886b8424e67f90b001e67
- Affected versionversion=66e3e591891da9899a8990792da080432531ffd4 <3ad5fbcced4e9c2b0fee3c1b76289a147fc35b89
- Affected versionversion=66e3e591891da9899a8990792da080432531ffd4 <5ec61fbef9ec5635c492ae63dfb5d13f2bdf1023
- Affected versionversion=66e3e591891da9899a8990792da080432531ffd4 <6c82f88bc7a8458d5c60f9b354c4d32d233f0cac
- Affected versionversion=66e3e591891da9899a8990792da080432531ffd4 <8f50613bff228272577893aa10a346a2f3063e49
- Affected versionversion=66e3e591891da9899a8990792da080432531ffd4 <abf76d3239dee97b66e7241ad04811f1ce562e28
- Affected versionversion=66e3e591891da9899a8990792da080432531ffd4 <f3e409476ad0703c54c14f245e4e143c8124e1bd
- Affected versionversion=66e3e591891da9899a8990792da080432531ffd4 <fe7a0f4be283b40dd592540027279735120d0d6f
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
No sourced classifications are available.
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