CVE-2026-64338: Linux kernel · USB: misc: uss720: unregister parport on probe failure
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in b4ecbdc4f8830f5586c4a5cfc384c00f20f8f8b3 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:19 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in b4ecbdc4f8830f5586c4a5cfc384c00f20f8f8b3, 93563243377f8e9b46cc94d9c4f06533dd31b141, 1712fd71a5aaf81e47c747f180535fa963ad7830 +12
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: USB: misc: uss720: unregister parport on probe failure uss720_probe() registers a parport before reading the 1284 register used to detect unsupported Belkin F5U002 adapters. If get_1284_register() fails, the error path drops the driver private data and the USB device reference, but leaves the parport device registered. Leaving the port registered is more than a private allocation leak: parport_register_port() has already reserved a parport number and registered the parport bus device, while pp->private_data still points at the private data that the common error path is about to release. Undo the pre-announce registration in the get_1284_register() failure branch before jumping to the common private-data cleanup path. Clear priv->pp first, matching the disconnect path and avoiding a stale pointer in the private data. This issue was identified during our ongoing static-analysis research while reviewing kernel code.
References
- git.kernel.org/stable/c/6bbb98bec71b577fda4f4b48f7aea5874b04a576 (opens in a new tab)
- git.kernel.org/stable/c/93563243377f8e9b46cc94d9c4f06533dd31b141 (opens in a new tab)
- git.kernel.org/stable/c/1712fd71a5aaf81e47c747f180535fa963ad7830 (opens in a new tab)
- git.kernel.org/stable/c/0b3073f40cc9f95d5ff0037eb0a06f5c1725a7ea (opens in a new tab)
- git.kernel.org/stable/c/5e62d7857fd51b908b8371062ee839739a086bbe (opens in a new tab)
- git.kernel.org/stable/c/729b68a5bad71220ae0914c8bdab9488ad5be6c8 (opens in a new tab)
- git.kernel.org/stable/c/48dd0b2ec9f2e97c486eb68cd0a64b25c1c3df3e (opens in a new tab)
- git.kernel.org/stable/c/b4ecbdc4f8830f5586c4a5cfc384c00f20f8f8b3 (opens in a new tab)