Answer in brief
CVE-2026-64343 records a Unknown severity vulnerability in USB: ldusb: 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-64343 records a Unknown severity vulnerability in USB: ldusb: 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 | >=ce0d7d3f575fc1ba6a89c3c651e710355590daff <fc55923a972e715f9a27187b47d4920709e23d85 || >=ce0d7d3f575fc1ba6a89c3c651e710355590daff <e5a9bdce4bfd3e2226b5f3df5fb8385d6935ee69 || >=ce0d7d3f575fc1ba6a89c3c651e710355590daff <af59829e67e11ba2511a9f8e4b9111afc7d1f550 || >=ce0d7d3f575fc1ba6a89c3c651e710355590daff <02ca08fff74cf9b0a3c4d2cacde1c6edeeb95bb4 || >=ce0d7d3f575fc1ba6a89c3c651e710355590daff <d8f69404e1d671326f86d378b9f5bfbd56490e9d || >=ce0d7d3f575fc1ba6a89c3c651e710355590daff <2107a4fc8ff1cf1d52f416c1e5cc8e97413a5915 || >=ce0d7d3f575fc1ba6a89c3c651e710355590daff <a3e794136ab5e3ad1e7019175a4b837aec86db4b || >=ce0d7d3f575fc1ba6a89c3c651e710355590daff <19bdfc7b3c179331eafa423d87e1336f43bbfeb8 | fc55923a972e715f9a27187b47d4920709e23d85, e5a9bdce4bfd3e2226b5f3df5fb8385d6935ee69, af59829e67e11ba2511a9f8e4b9111afc7d1f550, 02ca08fff74cf9b0a3c4d2cacde1c6edeeb95bb4, d8f69404e1d671326f86d378b9f5bfbd56490e9d, 2107a4fc8ff1cf1d52f416c1e5cc8e97413a5915, a3e794136ab5e3ad1e7019175a4b837aec86db4b, 19bdfc7b3c179331eafa423d87e1336f43bbfeb8 |
| Linux/Linuxgeneric | 2.6.26 | 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: ldusb: 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 | >=ce0d7d3f575fc1ba6a89c3c651e710355590daff <fc55923a972e715f9a27187b47d4920709e23d85 || >=ce0d7d3f575fc1ba6a89c3c651e710355590daff <e5a9bdce4bfd3e2226b5f3df5fb8385d6935ee69 || >=ce0d7d3f575fc1ba6a89c3c651e710355590daff <af59829e67e11ba2511a9f8e4b9111afc7d1f550 || >=ce0d7d3f575fc1ba6a89c3c651e710355590daff <02ca08fff74cf9b0a3c4d2cacde1c6edeeb95bb4 || >=ce0d7d3f575fc1ba6a89c3c651e710355590daff <d8f69404e1d671326f86d378b9f5bfbd56490e9d || >=ce0d7d3f575fc1ba6a89c3c651e710355590daff <2107a4fc8ff1cf1d52f416c1e5cc8e97413a5915 || >=ce0d7d3f575fc1ba6a89c3c651e710355590daff <a3e794136ab5e3ad1e7019175a4b837aec86db4b || >=ce0d7d3f575fc1ba6a89c3c651e710355590daff <19bdfc7b3c179331eafa423d87e1336f43bbfeb8 | fc55923a972e715f9a27187b47d4920709e23d85, e5a9bdce4bfd3e2226b5f3df5fb8385d6935ee69, af59829e67e11ba2511a9f8e4b9111afc7d1f550, 02ca08fff74cf9b0a3c4d2cacde1c6edeeb95bb4, d8f69404e1d671326f86d378b9f5bfbd56490e9d, 2107a4fc8ff1cf1d52f416c1e5cc8e97413a5915, a3e794136ab5e3ad1e7019175a4b837aec86db4b, 19bdfc7b3c179331eafa423d87e1336f43bbfeb8 |
| Linux/Linuxgeneric | 2.6.26 | 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: ldusb: 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.