Answer in brief
CVE-2026-64340 records a Unknown severity vulnerability in USB: legousbtower: fix use-after-free on disconnect race. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-64340 records a Unknown severity vulnerability in USB: legousbtower: fix use-after-free on disconnect race. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=18bcbcfe9ca2308ebffb40068b51803da9315d97 <11d069f85851997b4ea0adf242ed9672dc749b8f || >=18bcbcfe9ca2308ebffb40068b51803da9315d97 <b4222c05066b252b451f9c8c4730b5b60824ea66 || >=18bcbcfe9ca2308ebffb40068b51803da9315d97 <6462de75d2e370c7e74dcfb7b4ae79eb5a6a55ee || >=18bcbcfe9ca2308ebffb40068b51803da9315d97 <0b57e5ddbd89df3bc367463de3d2ca66f99a1a5e || >=18bcbcfe9ca2308ebffb40068b51803da9315d97 <ab2bfd7bec4f134b377ec42f513e90c35db94160 || >=18bcbcfe9ca2308ebffb40068b51803da9315d97 <766738ecf2b819e54d38763c8d1c8ae6cff14b39 || >=18bcbcfe9ca2308ebffb40068b51803da9315d97 <9ba62966461a8e3cc593b62c56ec62eb2d80436d || >=18bcbcfe9ca2308ebffb40068b51803da9315d97 <62fc8eb1b1481051f7bab4aa93d79809053dd09f | 11d069f85851997b4ea0adf242ed9672dc749b8f, b4222c05066b252b451f9c8c4730b5b60824ea66, 6462de75d2e370c7e74dcfb7b4ae79eb5a6a55ee, 0b57e5ddbd89df3bc367463de3d2ca66f99a1a5e, ab2bfd7bec4f134b377ec42f513e90c35db94160, 766738ecf2b819e54d38763c8d1c8ae6cff14b39, 9ba62966461a8e3cc593b62c56ec62eb2d80436d, 62fc8eb1b1481051f7bab4aa93d79809053dd09f |
| Linux/Linuxgeneric | 2.6.25 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
In the Linux kernel, the following vulnerability has been resolved: USB: legousbtower: fix use-after-free on disconnect race mutex_unlock() may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly (unlike spinlocks and refcounts). [1][2] Use a kref to release the driver data to avoid use-after-free in mutex_unlock() when release() races with disconnect(). [1] a51749ab34d9 ("locking/mutex: Document that mutex_unlock() is non-atomic") [2] 2b9d9e0a9ba0 ("locking/mutex: Clarify that mutex_unlock(), and most other sleeping locks, can still use the lock object after it's unlocked")
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=18bcbcfe9ca2308ebffb40068b51803da9315d97 <11d069f85851997b4ea0adf242ed9672dc749b8f || >=18bcbcfe9ca2308ebffb40068b51803da9315d97 <b4222c05066b252b451f9c8c4730b5b60824ea66 || >=18bcbcfe9ca2308ebffb40068b51803da9315d97 <6462de75d2e370c7e74dcfb7b4ae79eb5a6a55ee || >=18bcbcfe9ca2308ebffb40068b51803da9315d97 <0b57e5ddbd89df3bc367463de3d2ca66f99a1a5e || >=18bcbcfe9ca2308ebffb40068b51803da9315d97 <ab2bfd7bec4f134b377ec42f513e90c35db94160 || >=18bcbcfe9ca2308ebffb40068b51803da9315d97 <766738ecf2b819e54d38763c8d1c8ae6cff14b39 || >=18bcbcfe9ca2308ebffb40068b51803da9315d97 <9ba62966461a8e3cc593b62c56ec62eb2d80436d || >=18bcbcfe9ca2308ebffb40068b51803da9315d97 <62fc8eb1b1481051f7bab4aa93d79809053dd09f | 11d069f85851997b4ea0adf242ed9672dc749b8f, b4222c05066b252b451f9c8c4730b5b60824ea66, 6462de75d2e370c7e74dcfb7b4ae79eb5a6a55ee, 0b57e5ddbd89df3bc367463de3d2ca66f99a1a5e, ab2bfd7bec4f134b377ec42f513e90c35db94160, 766738ecf2b819e54d38763c8d1c8ae6cff14b39, 9ba62966461a8e3cc593b62c56ec62eb2d80436d, 62fc8eb1b1481051f7bab4aa93d79809053dd09f |
| Linux/Linuxgeneric | 2.6.25 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 11, 2026
In the Linux kernel, the following vulnerability has been resolved: USB: legousbtower: fix use-after-free on disconnect race mutex_unlock() may access the mutex structure after releasing the lock and therefore cannot be used to manage lifetime of objects directly (unlike spinlocks and refcounts). [1][2] Use a kref to release the driver data to avoid use-after-free in mutex_unlock() when release() races with disconnect(). [1] a51749ab34d9 ("locking/mutex: Document that mutex_unlock() is non-atomic") [2] 2b9d9e0a9ba0 ("locking/mutex: Clarify that mutex_unlock(), and most other sleeping locks, can still use the lock object after it's unlocked")
Quoted source text, attributed separately from HOL analysis.