Memory leak via failed ULPI device registration
Published Jul 25, 2026 · Updated Jul 25, 2026
Memory leak in the USB ULPI registration path in Linux Kernel 4.2 and later leaves allocated device-name memory unreleased after failures. The registration error paths allocate a device name but do not initialize the device structure soon enough to release its initial reference when registration aborts. The public record identifies no attacker-controlled trigger or resulting crash, so reachability and operational consequence remain unspecified.
Summary
What happened
Memory leak in the USB ULPI registration path in Linux Kernel 4.2 and later leaves allocated device-name memory unreleased after failures. The registration error paths allocate a device name but do not initialize the device structure soon enough to release its initial reference when registration aborts. The public record identifies no attacker-controlled trigger or resulting crash, so reachability and operational consequence remain unspecified.
The record
- CVE
- CVE-2026-64332
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f <1967a7f0cd5c08eb479196daa5aaa4b7b7a7bd04
- Affected versionversion=289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f <5c098f20f15db7f9126129686d1c6da2ce8bbeb0
- Affected versionversion=289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f <624c57147df1977e0d3da53f1da7117861b9cf19
- Affected versionversion=289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f <691e61e5d4cfc5a1b061e937f8cbf2126bfc19a0
- Affected versionversion=289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f <88187a43135c79d0e43573b4d8f880bbb919eceb
- Affected versionversion=289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f <8af6812795869a66e9b26044f455b13deecdb69c
- Affected versionversion=289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f <d5b32f36c50894ac2df8fa184e6f35f3a6665ecd
- Affected versionversion=289fcff4bcdb1dcc0ce8788b7ea0f58a9e4a495f <e5493c9a98ffe083acf13ac064828ae598ba3c16
- Affected versionversion=4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo