Unspecified impact via USB disconnect use-after-free
Published Jul 25, 2026 · Updated Jul 25, 2026
Use-after-free in the Linux Kernel idmouse USB driver allows local users to trigger unspecified impact through a disconnect race. The idmouse release path frees driver data before mutex_unlock() has finished accessing its embedded mutex, leaving mutex_unlock() to use released storage when release() races with disconnection. Triggering requires local access and a release() operation concurrent with device disconnection; the published record does not establish a crash, code execution, or another specific consequence.
Summary
What happened
Use-after-free in the Linux Kernel idmouse USB driver allows local users to trigger unspecified impact through a disconnect race. The idmouse release path frees driver data before mutex_unlock() has finished accessing its embedded mutex, leaving mutex_unlock() to use released storage when release() races with disconnection. Triggering requires local access and a release() operation concurrent with device disconnection; the published record does not establish a crash, code execution, or another specific consequence.
The record
- CVE
- CVE-2026-64344
- 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=2.6.24
- Affected versionversion=54d2bc068fd21bcb096660938bce7c7265613a24 <31e75fed8f90cfea9f8285e7ed135b0e452bf872
- Affected versionversion=54d2bc068fd21bcb096660938bce7c7265613a24 <54c2b7356b4aeea467f9fb13b85e9e036bc428cb
- Affected versionversion=54d2bc068fd21bcb096660938bce7c7265613a24 <60fc5ef4ecea3e3d1fe556cecf53ddd13096ef09
- Affected versionversion=54d2bc068fd21bcb096660938bce7c7265613a24 <8d53b14ad4ccbff6d306b3a39c812303f4a87d41
- Affected versionversion=54d2bc068fd21bcb096660938bce7c7265613a24 <d0f61acb51a8c8f3fd41c303ddb7770cd83e7ed4
- Affected versionversion=54d2bc068fd21bcb096660938bce7c7265613a24 <e88cff5fbaa629f3cab45c8b46f395d62c2eb515
- Affected versionversion=54d2bc068fd21bcb096660938bce7c7265613a24 <f62622e947f82a3854a8502d09492ffbdeb252b4
- Affected versionversion=54d2bc068fd21bcb096660938bce7c7265613a24 <ff002c153f9722caece3983cc23dc4d9d4652cb4
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