NVD / CVE Program· CNA Linux

CVE-2026-64340: USB: legousbtower: 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 0b57e5ddbd89df3bc367463de3d2ca66f99a1a5e, 11d069f85851997b4ea0adf242ed9672dc749b8f, 62fc8eb1b1481051f7bab4aa93d79809053dd09f.

Low priority for now. Upgrade to Linux Linux 0b57e5ddbd89df3bc367463de3d2ca66f99a1a5e, 11d069f85851997b4ea0adf242ed9672dc749b8f, 62fc8eb1b1481051f7bab4aa93d79809053dd09f 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: legousbtower: 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")

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

Published: Jul 25, 2026
Updated: Sep 3, 2026
EPSS: 0.1% · 2th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

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.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel2.6.25 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 kernel7.2

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.25affected
- 18bcbcfe9ca2308ebffb40068b51803da9315d97 and later · before 11d069f85851997b4ea0adf242ed9672dc749b8faffected · git
- 18bcbcfe9ca2308ebffb40068b51803da9315d97 and later · before b4222c05066b252b451f9c8c4730b5b60824ea66affected · git
- 18bcbcfe9ca2308ebffb40068b51803da9315d97 and later · before 6462de75d2e370c7e74dcfb7b4ae79eb5a6a55eeaffected · git
- 18bcbcfe9ca2308ebffb40068b51803da9315d97 and later · before 0b57e5ddbd89df3bc367463de3d2ca66f99a1a5eaffected · git
- 18bcbcfe9ca2308ebffb40068b51803da9315d97 and later · before ab2bfd7bec4f134b377ec42f513e90c35db94160affected · git
- 18bcbcfe9ca2308ebffb40068b51803da9315d97 and later · before 766738ecf2b819e54d38763c8d1c8ae6cff14b39affected · git
- 18bcbcfe9ca2308ebffb40068b51803da9315d97 and later · before 9ba62966461a8e3cc593b62c56ec62eb2d80436daffected · git
- 18bcbcfe9ca2308ebffb40068b51803da9315d97 and later · before 62fc8eb1b1481051f7bab4aa93d79809053dd09faffected · git
- before 2.6.25not affected · semver

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 records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
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 KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2026-64338Jul 25, 2026 · USB: misc: uss720: unregister parport on probe failure
22Monitor
← EarlierCVE-2026-64339Jul 25, 2026 · usb: misc: usbio: bound bulk IN response length to the received transfer
28Monitor
Later →CVE-2026-64342Jul 25, 2026 · USB: iowarrior: fix use-after-free on disconnect
31Monitor

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	0b57e5ddbd89df3bc367463de3d2ca66f99a1a5e	Vendor (CNA)
Linux Linux	11d069f85851997b4ea0adf242ed9672dc749b8f	Vendor (CNA)
Linux Linux	62fc8eb1b1481051f7bab4aa93d79809053dd09f	Vendor (CNA)
Linux Linux	6462de75d2e370c7e74dcfb7b4ae79eb5a6a55ee	Vendor (CNA)
Linux Linux	766738ecf2b819e54d38763c8d1c8ae6cff14b39	Vendor (CNA)
Linux Linux	9ba62966461a8e3cc593b62c56ec62eb2d80436d	Vendor (CNA)
Linux Linux	ab2bfd7bec4f134b377ec42f513e90c35db94160	Vendor (CNA)
Linux Linux	b4222c05066b252b451f9c8c4730b5b60824ea66	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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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 Free

CVSS 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 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&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

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/0b57e5ddbd89df3bc367463de3d2ca66f99a1a5e

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records