CVE-2026-46109: Linux kernel · usb: ulpi: fix memory leak on ulpi_register() error paths
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f30ccfc2985590b33a23a3d8bed7ca16c0af551b : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:34 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 f30ccfc2985590b33a23a3d8bed7ca16c0af551b, f1b855c00988a9cb41134cab7cf9faedba775dd9, be2c1d825f54277472c87019e82013ac534ddc4c +12
Exploitation evidence
Disclosed: evidence found.
CVE published 28 May 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: ulpi: fix memory leak on ulpi_register() error paths Commit 01af542392b5 ("usb: ulpi: fix double free in ulpi_register_interface() error path") removed kfree(ulpi) from ulpi_register_interface() to fix a double-free when device_register() fails. But when ulpi_of_register() or ulpi_read_id() fail before device_register() is called, the ulpi allocation is leaked. Add kfree(ulpi) on both error paths to properly clean up the allocation.
References
- git.kernel.org/stable/c/0c2c0c6820fe96fa4be0a0499f8d3f3321b9af6c (opens in a new tab)
- git.kernel.org/stable/c/f1b855c00988a9cb41134cab7cf9faedba775dd9 (opens in a new tab)
- git.kernel.org/stable/c/7bd61ed0bf9f4f1f2673d489b3bda1555b48d054 (opens in a new tab)
- git.kernel.org/stable/c/b0c0d44adb55c66663886cb6e30ee92cbb0f5385 (opens in a new tab)
- git.kernel.org/stable/c/be2c1d825f54277472c87019e82013ac534ddc4c (opens in a new tab)
- git.kernel.org/stable/c/2a71e01b2cf9b4329ff67102c1bea7448c2a2d2d (opens in a new tab)
- git.kernel.org/stable/c/f30ccfc2985590b33a23a3d8bed7ca16c0af551b (opens in a new tab)
- git.kernel.org/stable/c/0b9fcab1b8608d429e5f239afb197de928d4de7d (opens in a new tab)