7.8
CVE-2026-64344
- EPSS 0.18%
- Veröffentlicht 25.07.2026 08:50:06
- Zuletzt bearbeitet 03.09.2026 16:01:33
- Erkennungen
USB: idmouse: fix use-after-free on disconnect race
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")Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Linux ≫ Linux Kernel Version >= 2.6.24.1 < 5.10.261
Linux ≫ Linux Kernel Version >= 5.11 < 5.15.212
Linux ≫ Linux Kernel Version >= 5.16 < 6.1.178
Linux ≫ Linux Kernel Version >= 6.2 < 6.6.145
Linux ≫ Linux Kernel Version >= 6.7 < 6.12.96
Linux ≫ Linux Kernel Version >= 6.13 < 6.18.39
Linux ≫ Linux Kernel Version >= 6.19 < 7.1.4
Linux ≫ Linux Kernel Version 2.6.24 Update -
Linux ≫ Linux Kernel Version 2.6.24 Update rc2
Linux ≫ Linux Kernel Version 2.6.24 Update rc3
Linux ≫ Linux Kernel Version 2.6.24 Update rc4
Linux ≫ Linux Kernel Version 2.6.24 Update rc5
Linux ≫ Linux Kernel Version 2.6.24 Update rc6
Linux ≫ Linux Kernel Version 2.6.24 Update rc7
Linux ≫ Linux Kernel Version 2.6.24 Update rc8
Linux ≫ Linux Kernel Version 7.2 Update rc1
Linux ≫ Linux Kernel Version 7.2 Update rc2
VulnDex Vulnerability Enrichment
| Typ | Quelle | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.18% | 0.075 |
| Quelle | Base Score | Exploit Score | Impact Score | Vector String |
|---|---|---|---|---|
| NIST | 7.8 | 1.8 | 5.9 |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
|
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
https://git.kernel.org/stable/c/31e75fed8f90cfea9f8285e7ed135b0e452bf872
https://git.kernel.org/stable/c/8d53b14ad4ccbff6d306b3a39c812303f4a87d41
https://git.kernel.org/stable/c/f62622e947f82a3854a8502d09492ffbdeb252b4
https://git.kernel.org/stable/c/60fc5ef4ecea3e3d1fe556cecf53ddd13096ef09
https://git.kernel.org/stable/c/d0f61acb51a8c8f3fd41c303ddb7770cd83e7ed4
https://git.kernel.org/stable/c/54c2b7356b4aeea467f9fb13b85e9e036bc428cb
https://git.kernel.org/stable/c/e88cff5fbaa629f3cab45c8b46f395d62c2eb515
https://git.kernel.org/stable/c/ff002c153f9722caece3983cc23dc4d9d4652cb4