In the Linux kernel, the following vulnerability has been resolved: USB: idmouse: fix use-after-free on disconnect race mutex_unlock() may access… (CVE-2026-64344)
A use-after-free vulnerability in the Linux kernel's USB idmouse driver was resolved. The issue arises because mutex_unlock() may access the mutex structure after releasing the lock, which can lead to unsafe object lifetime management. The fix involved using a kernel reference count (kref) to properly manage driver data release, preventing use-after-free conditions when release() races with disconnect().
AI Analysis
Technical Summary
The vulnerability in the Linux kernel USB idmouse driver is due to improper handling of object lifetime in the context of mutex_unlock(). Unlike spinlocks and refcounts, mutex_unlock() can access the mutex object after unlocking, making it unsafe to manage object lifetime directly with it. This led to a use-after-free condition when the release() function races with disconnect(). The patch replaced direct lifetime management via mutex_unlock() with a kref-based mechanism to safely release driver data, eliminating the race condition and use-after-free.
Potential Impact
The vulnerability could cause use-after-free conditions in the kernel USB idmouse driver, potentially leading to kernel crashes or undefined behavior. No known exploits in the wild have been reported. The impact is limited to the affected driver and kernel context where the race condition occurs.
Mitigation Recommendations
A fix has been implemented in the Linux kernel source to address this issue by using kref for driver data release instead of relying on mutex_unlock() for object lifetime management. Users should update to the fixed kernel versions once available. Patch status is not yet confirmed in this data; check the official Linux kernel advisories or vendor updates for the specific fixed versions and apply them accordingly.
In the Linux kernel, the following vulnerability has been resolved: USB: idmouse: fix use-after-free on disconnect race mutex_unlock() may access… (CVE-2026-64344)
Description
A use-after-free vulnerability in the Linux kernel's USB idmouse driver was resolved. The issue arises because mutex_unlock() may access the mutex structure after releasing the lock, which can lead to unsafe object lifetime management. The fix involved using a kernel reference count (kref) to properly manage driver data release, preventing use-after-free conditions when release() races with disconnect().
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel USB idmouse driver is due to improper handling of object lifetime in the context of mutex_unlock(). Unlike spinlocks and refcounts, mutex_unlock() can access the mutex object after unlocking, making it unsafe to manage object lifetime directly with it. This led to a use-after-free condition when the release() function races with disconnect(). The patch replaced direct lifetime management via mutex_unlock() with a kref-based mechanism to safely release driver data, eliminating the race condition and use-after-free.
Potential Impact
The vulnerability could cause use-after-free conditions in the kernel USB idmouse driver, potentially leading to kernel crashes or undefined behavior. No known exploits in the wild have been reported. The impact is limited to the affected driver and kernel context where the race condition occurs.
Mitigation Recommendations
A fix has been implemented in the Linux kernel source to address this issue by using kref for driver data release instead of relying on mutex_unlock() for object lifetime management. Users should update to the fixed kernel versions once available. Patch status is not yet confirmed in this data; check the official Linux kernel advisories or vendor updates for the specific fixed versions and apply them accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-fpmv-m5rr-683w
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64344"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420c9c2644c7f808506a
Added to database: 07/25/2026, 23:09:00 UTC
Last enriched: 07/25/2026, 23:32:17 UTC
Last updated: 07/26/2026, 04:26:21 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.