CVE-2026-64344: USB: idmouse: fix use-after-free on disconnect race
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 31e75fed8f90cfea9f8285e7ed135b0e452bf872, 54c2b7356b4aeea467f9fb13b85e9e036bc428cb, 60fc5ef4ecea3e3d1fe556cecf53ddd13096ef09.
Low priority for now. Upgrade to Linux Linux 31e75fed8f90cfea9f8285e7ed135b0e452bf872, 54c2b7356b4aeea467f9fb13b85e9e036bc428cb, 60fc5ef4ecea3e3d1fe556cecf53ddd13096ef09 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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")
- Published
- Jul 25, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.24affected
- 54d2bc068fd21bcb096660938bce7c7265613a24 and later · before 31e75fed8f90cfea9f8285e7ed135b0e452bf872affected · git
- 54d2bc068fd21bcb096660938bce7c7265613a24 and later · before 8d53b14ad4ccbff6d306b3a39c812303f4a87d41affected · git
- 54d2bc068fd21bcb096660938bce7c7265613a24 and later · before f62622e947f82a3854a8502d09492ffbdeb252b4affected · git
- 54d2bc068fd21bcb096660938bce7c7265613a24 and later · before 60fc5ef4ecea3e3d1fe556cecf53ddd13096ef09affected · git
- 54d2bc068fd21bcb096660938bce7c7265613a24 and later · before d0f61acb51a8c8f3fd41c303ddb7770cd83e7ed4affected · git
- 54d2bc068fd21bcb096660938bce7c7265613a24 and later · before 54c2b7356b4aeea467f9fb13b85e9e036bc428cbaffected · git
- 54d2bc068fd21bcb096660938bce7c7265613a24 and later · before e88cff5fbaa629f3cab45c8b46f395d62c2eb515affected · git
- 54d2bc068fd21bcb096660938bce7c7265613a24 and later · before ff002c153f9722caece3983cc23dc4d9d4652cb4affected · git
- before 2.6.24not affected · semver
Affected versions · NVD (9)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.24.1 and later · before 5.10.261
- linux linux kernel5.11 and later · before 5.15.212
- linux linux kernel5.16 and later · before 6.1.178
- linux linux kernel6.2 and later · before 6.6.145
- linux linux kernel6.7 and later · before 6.12.96
- linux linux kernel6.13 and later · before 6.18.39
- linux linux kernel6.19 and later · before 7.1.4
- linux linux kernel2.6.24
- linux linux kernel7.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-64342Jul 25, 2026 · USB: iowarrior: fix use-after-free on disconnect31Monitor
- ← EarlierCVE-2026-64343Jul 25, 2026 · USB: ldusb: fix use-after-free on disconnect race31Monitor
- Later →CVE-2026-64345Jul 25, 2026 · usb: gadget: f_printer: take kref only for successful open22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 31e75fed8f90cfea9f8285e7ed135b0e452bf872 | Vendor (CNA) |
| Linux Linux | 54c2b7356b4aeea467f9fb13b85e9e036bc428cb | Vendor (CNA) |
| Linux Linux | 60fc5ef4ecea3e3d1fe556cecf53ddd13096ef09 | Vendor (CNA) |
| Linux Linux | 8d53b14ad4ccbff6d306b3a39c812303f4a87d41 | Vendor (CNA) |
| Linux Linux | d0f61acb51a8c8f3fd41c303ddb7770cd83e7ed4 | Vendor (CNA) |
| Linux Linux | e88cff5fbaa629f3cab45c8b46f395d62c2eb515 | Vendor (CNA) |
| Linux Linux | f62622e947f82a3854a8502d09492ffbdeb252b4 | Vendor (CNA) |
| Linux Linux | ff002c153f9722caece3983cc23dc4d9d4652cb4 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/54c2b7356b4aeea467f9fb13b85e9e036bc428cb
- git.kernel.org/stable/c/60fc5ef4ecea3e3d1fe556cecf53ddd13096ef09
- git.kernel.org/stable/c/8d53b14ad4ccbff6d306b3a39c812303f4a87d41
- git.kernel.org/stable/c/d0f61acb51a8c8f3fd41c303ddb7770cd83e7ed4
- git.kernel.org/stable/c/e88cff5fbaa629f3cab45c8b46f395d62c2eb515
- git.kernel.org/stable/c/f62622e947f82a3854a8502d09492ffbdeb252b4
- git.kernel.org/stable/c/ff002c153f9722caece3983cc23dc4d9d4652cb4
Vendor advisories and official records. Exploit/PoC links are deliberately left out.