In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect race mutex_unlock() may access… (CVE-2026-64341)
A use-after-free vulnerability in the Linux kernel's USB iowarrior driver was resolved. The issue involved mutex_unlock() accessing the mutex structure after releasing the lock, which could lead to unsafe memory access when release() races with disconnect(). The fix uses a kref to manage driver data lifetime safely, preventing use-after-free conditions.
AI Analysis
Technical Summary
The Linux kernel's USB iowarrior driver had a use-after-free vulnerability caused by improper handling of mutex_unlock(). Unlike spinlocks and refcounts, mutex_unlock() may access the mutex object after unlocking, making it unsafe to manage object lifetime directly with it. This could cause a race condition between release() and disconnect() leading to use-after-free. The vulnerability was fixed by introducing a kref-based reference counting mechanism to safely release driver data, avoiding the unsafe access pattern.
Potential Impact
This vulnerability could lead to use-after-free conditions in kernel space, potentially causing system instability or crashes. However, no known exploits in the wild have been reported. The impact is limited to the USB iowarrior driver within the Linux kernel.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by using kref for driver data lifetime management. Users should update to a kernel version that includes this fix once available. Patch status is not explicitly stated; check the vendor advisory or Linux kernel release notes for the specific fixed version.
In the Linux kernel, the following vulnerability has been resolved: USB: iowarrior: fix use-after-free on disconnect race mutex_unlock() may access… (CVE-2026-64341)
Description
A use-after-free vulnerability in the Linux kernel's USB iowarrior driver was resolved. The issue involved mutex_unlock() accessing the mutex structure after releasing the lock, which could lead to unsafe memory access when release() races with disconnect(). The fix uses a kref to manage driver data lifetime safely, preventing use-after-free conditions.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's USB iowarrior driver had a use-after-free vulnerability caused by improper handling of mutex_unlock(). Unlike spinlocks and refcounts, mutex_unlock() may access the mutex object after unlocking, making it unsafe to manage object lifetime directly with it. This could cause a race condition between release() and disconnect() leading to use-after-free. The vulnerability was fixed by introducing a kref-based reference counting mechanism to safely release driver data, avoiding the unsafe access pattern.
Potential Impact
This vulnerability could lead to use-after-free conditions in kernel space, potentially causing system instability or crashes. However, no known exploits in the wild have been reported. The impact is limited to the USB iowarrior driver within the Linux kernel.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by using kref for driver data lifetime management. Users should update to a kernel version that includes this fix once available. Patch status is not explicitly stated; check the vendor advisory or Linux kernel release notes for the specific fixed version.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-jfg4-c35c-vjq6
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64341"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420d9c2644c7f80859c1
Added to database: 07/25/2026, 23:09:01 UTC
Last enriched: 07/25/2026, 23:34:57 UTC
Last updated: 07/26/2026, 03:58:56 UTC
Views: 4
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.