Answer in brief
CVE-2026-64344 records a Unknown severity vulnerability in USB: idmouse: 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-64344 records a Unknown severity vulnerability in USB: idmouse: 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 | >=54d2bc068fd21bcb096660938bce7c7265613a24 <31e75fed8f90cfea9f8285e7ed135b0e452bf872 || >=54d2bc068fd21bcb096660938bce7c7265613a24 <8d53b14ad4ccbff6d306b3a39c812303f4a87d41 || >=54d2bc068fd21bcb096660938bce7c7265613a24 <f62622e947f82a3854a8502d09492ffbdeb252b4 || >=54d2bc068fd21bcb096660938bce7c7265613a24 <60fc5ef4ecea3e3d1fe556cecf53ddd13096ef09 || >=54d2bc068fd21bcb096660938bce7c7265613a24 <d0f61acb51a8c8f3fd41c303ddb7770cd83e7ed4 || >=54d2bc068fd21bcb096660938bce7c7265613a24 <54c2b7356b4aeea467f9fb13b85e9e036bc428cb || >=54d2bc068fd21bcb096660938bce7c7265613a24 <e88cff5fbaa629f3cab45c8b46f395d62c2eb515 || >=54d2bc068fd21bcb096660938bce7c7265613a24 <ff002c153f9722caece3983cc23dc4d9d4652cb4 | 31e75fed8f90cfea9f8285e7ed135b0e452bf872, 8d53b14ad4ccbff6d306b3a39c812303f4a87d41, f62622e947f82a3854a8502d09492ffbdeb252b4, 60fc5ef4ecea3e3d1fe556cecf53ddd13096ef09, d0f61acb51a8c8f3fd41c303ddb7770cd83e7ed4, 54c2b7356b4aeea467f9fb13b85e9e036bc428cb, e88cff5fbaa629f3cab45c8b46f395d62c2eb515, ff002c153f9722caece3983cc23dc4d9d4652cb4 |
| Linux/Linuxgeneric | 2.6.24 | 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: idmouse: 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 | >=54d2bc068fd21bcb096660938bce7c7265613a24 <31e75fed8f90cfea9f8285e7ed135b0e452bf872 || >=54d2bc068fd21bcb096660938bce7c7265613a24 <8d53b14ad4ccbff6d306b3a39c812303f4a87d41 || >=54d2bc068fd21bcb096660938bce7c7265613a24 <f62622e947f82a3854a8502d09492ffbdeb252b4 || >=54d2bc068fd21bcb096660938bce7c7265613a24 <60fc5ef4ecea3e3d1fe556cecf53ddd13096ef09 || >=54d2bc068fd21bcb096660938bce7c7265613a24 <d0f61acb51a8c8f3fd41c303ddb7770cd83e7ed4 || >=54d2bc068fd21bcb096660938bce7c7265613a24 <54c2b7356b4aeea467f9fb13b85e9e036bc428cb || >=54d2bc068fd21bcb096660938bce7c7265613a24 <e88cff5fbaa629f3cab45c8b46f395d62c2eb515 || >=54d2bc068fd21bcb096660938bce7c7265613a24 <ff002c153f9722caece3983cc23dc4d9d4652cb4 | 31e75fed8f90cfea9f8285e7ed135b0e452bf872, 8d53b14ad4ccbff6d306b3a39c812303f4a87d41, f62622e947f82a3854a8502d09492ffbdeb252b4, 60fc5ef4ecea3e3d1fe556cecf53ddd13096ef09, d0f61acb51a8c8f3fd41c303ddb7770cd83e7ed4, 54c2b7356b4aeea467f9fb13b85e9e036bc428cb, e88cff5fbaa629f3cab45c8b46f395d62c2eb515, ff002c153f9722caece3983cc23dc4d9d4652cb4 |
| Linux/Linuxgeneric | 2.6.24 | 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: idmouse: 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.