In the Linux kernel, the following vulnerability has been resolved: USB: legousbtower: fix use-after-free on disconnect race mutex_unlock() may… (CVE-2026-64340)
A use-after-free vulnerability in the Linux kernel's USB legousbtower 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 involves using a kernel reference count (kref) to safely release driver data, preventing use-after-free conditions during races between release() and disconnect() operations.
AI Analysis
Technical Summary
The Linux kernel's USB legousbtower driver had a use-after-free vulnerability caused by improper handling of mutex_unlock(). Unlike spinlocks and refcounts, mutex_unlock() can access the mutex structure after unlocking, making it unsafe to manage object lifetimes directly. This flaw could cause a race condition between the release() and disconnect() functions, potentially leading to use-after-free errors. The vulnerability was addressed by switching to a kref-based mechanism to manage driver data release safely, eliminating the unsafe access pattern.
Potential Impact
The vulnerability could lead to use-after-free conditions in the Linux kernel USB driver, which may cause system instability or crashes. No known exploits in the wild have been reported. The impact is limited to kernel-level USB driver operations involving the legousbtower device.
Mitigation Recommendations
A fix has been implemented in the Linux kernel by replacing mutex_unlock()-based lifetime management with a kref-based approach. Users should apply the official Linux kernel updates that include this patch. Since no explicit patch links or vendor advisories are provided, check the Linux kernel mailing lists or official repositories for the relevant commit and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: USB: legousbtower: fix use-after-free on disconnect race mutex_unlock() may… (CVE-2026-64340)
Description
A use-after-free vulnerability in the Linux kernel's USB legousbtower 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 involves using a kernel reference count (kref) to safely release driver data, preventing use-after-free conditions during races between release() and disconnect() operations.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's USB legousbtower driver had a use-after-free vulnerability caused by improper handling of mutex_unlock(). Unlike spinlocks and refcounts, mutex_unlock() can access the mutex structure after unlocking, making it unsafe to manage object lifetimes directly. This flaw could cause a race condition between the release() and disconnect() functions, potentially leading to use-after-free errors. The vulnerability was addressed by switching to a kref-based mechanism to manage driver data release safely, eliminating the unsafe access pattern.
Potential Impact
The vulnerability could lead to use-after-free conditions in the Linux kernel USB driver, which may cause system instability or crashes. No known exploits in the wild have been reported. The impact is limited to kernel-level USB driver operations involving the legousbtower device.
Mitigation Recommendations
A fix has been implemented in the Linux kernel by replacing mutex_unlock()-based lifetime management with a kref-based approach. Users should apply the official Linux kernel updates that include this patch. Since no explicit patch links or vendor advisories are provided, check the Linux kernel mailing lists or official repositories for the relevant commit and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-p757-fg2x-77h8
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64340"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420c9c2644c7f8085021
Added to database: 07/25/2026, 23:09:00 UTC
Last enriched: 07/25/2026, 23:31:36 UTC
Last updated: 07/26/2026, 05:14:37 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.