Answer in brief
CVE-2026-64341 records a Unknown severity vulnerability in USB: iowarrior: 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 | >=946b960d13c15f050a3b848987aaca79f6a459b7 <3c0a7b29ebb391d5f50b115e86f842b709195b08 || >=946b960d13c15f050a3b848987aaca79f6a459b7 <71590982700fdeb39a37a500c877228b0140978e || >=946b960d13c15f050a3b848987aaca79f6a459b7 <c602254ba4c10f60a73cd99d147874f86a3f485c | 3c0a7b29ebb391d5f50b115e86f842b709195b08, 71590982700fdeb39a37a500c877228b0140978e, c602254ba4c10f60a73cd99d147874f86a3f485c |
| Linux/Linuxgeneric | 2.6.21 | 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: iowarrior: 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.
Answer in brief
CVE-2026-64341 records a Unknown severity vulnerability in USB: iowarrior: 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 | >=946b960d13c15f050a3b848987aaca79f6a459b7 <3c0a7b29ebb391d5f50b115e86f842b709195b08 || >=946b960d13c15f050a3b848987aaca79f6a459b7 <71590982700fdeb39a37a500c877228b0140978e || >=946b960d13c15f050a3b848987aaca79f6a459b7 <c602254ba4c10f60a73cd99d147874f86a3f485c | 3c0a7b29ebb391d5f50b115e86f842b709195b08, 71590982700fdeb39a37a500c877228b0140978e, c602254ba4c10f60a73cd99d147874f86a3f485c |
| Linux/Linuxgeneric | 2.6.21 | 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: iowarrior: 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.