Answer in brief
CVE-2026-46109 records a Medium severity (CVSS 5.5) vulnerability in usb: ulpi: fix memory leak on ulpi_register() error paths. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-46109 records a Medium severity (CVSS 5.5) vulnerability in usb: ulpi: fix memory leak on ulpi_register() error paths. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2f70ba9dae13a190673cc3f9b4aad52179738f60 <0c2c0c6820fe96fa4be0a0499f8d3f3321b9af6c || >=ee248e6e941e4f2e634df2bd43e5f1ef810ab6df <f1b855c00988a9cb41134cab7cf9faedba775dd9 || >=272a9b26c336a295e4e209157fed809706c1b1f7 <7bd61ed0bf9f4f1f2673d489b3bda1555b48d054 || >=aaeae6533d77e6ed4def85baec01e2815ebbef61 <b0c0d44adb55c66663886cb6e30ee92cbb0f5385 || >=8763f8317bb389aded32a32b08f6751cfff657d2 <be2c1d825f54277472c87019e82013ac534ddc4c || >=38c28fe25611099230f0965c925499bfcf46a795 <2a71e01b2cf9b4329ff67102c1bea7448c2a2d2d || >=01af542392b5d41fd659d487015a71f627accce3 <f30ccfc2985590b33a23a3d8bed7ca16c0af551b || >=01af542392b5d41fd659d487015a71f627accce3 <0b9fcab1b8608d429e5f239afb197de928d4de7d || a6e5461f076c2ef63159f18e5cdbd30b50f0bc15 || >=5.10.253 <5.10.258 || >=5.15.203 <5.15.209 || >=6.1.168 <6.1.175 || >=6.6.134 <6.6.140 || >=6.12.81 <6.12.88 || >=6.18.22 <6.18.30 || >=6.19.12 <6.20 | 0c2c0c6820fe96fa4be0a0499f8d3f3321b9af6c, f1b855c00988a9cb41134cab7cf9faedba775dd9, 7bd61ed0bf9f4f1f2673d489b3bda1555b48d054, b0c0d44adb55c66663886cb6e30ee92cbb0f5385, be2c1d825f54277472c87019e82013ac534ddc4c, 2a71e01b2cf9b4329ff67102c1bea7448c2a2d2d, f30ccfc2985590b33a23a3d8bed7ca16c0af551b, 0b9fcab1b8608d429e5f239afb197de928d4de7d, 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.88, 6.18.30, 6.20 |
| Linux/Linuxgeneric | 7.0 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2f70ba9dae13a190673cc3f9b4aad52179738f60 <0c2c0c6820fe96fa4be0a0499f8d3f3321b9af6c || >=ee248e6e941e4f2e634df2bd43e5f1ef810ab6df <f1b855c00988a9cb41134cab7cf9faedba775dd9 || >=272a9b26c336a295e4e209157fed809706c1b1f7 <7bd61ed0bf9f4f1f2673d489b3bda1555b48d054 || >=aaeae6533d77e6ed4def85baec01e2815ebbef61 <b0c0d44adb55c66663886cb6e30ee92cbb0f5385 || >=8763f8317bb389aded32a32b08f6751cfff657d2 <be2c1d825f54277472c87019e82013ac534ddc4c || >=38c28fe25611099230f0965c925499bfcf46a795 <2a71e01b2cf9b4329ff67102c1bea7448c2a2d2d || >=01af542392b5d41fd659d487015a71f627accce3 <f30ccfc2985590b33a23a3d8bed7ca16c0af551b || >=01af542392b5d41fd659d487015a71f627accce3 <0b9fcab1b8608d429e5f239afb197de928d4de7d || a6e5461f076c2ef63159f18e5cdbd30b50f0bc15 || >=5.10.253 <5.10.258 || >=5.15.203 <5.15.209 || >=6.1.168 <6.1.175 || >=6.6.134 <6.6.140 || >=6.12.81 <6.12.88 || >=6.18.22 <6.18.30 || >=6.19.12 <6.20 | 0c2c0c6820fe96fa4be0a0499f8d3f3321b9af6c, f1b855c00988a9cb41134cab7cf9faedba775dd9, 7bd61ed0bf9f4f1f2673d489b3bda1555b48d054, b0c0d44adb55c66663886cb6e30ee92cbb0f5385, be2c1d825f54277472c87019e82013ac534ddc4c, 2a71e01b2cf9b4329ff67102c1bea7448c2a2d2d, f30ccfc2985590b33a23a3d8bed7ca16c0af551b, 0b9fcab1b8608d429e5f239afb197de928d4de7d, 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.88, 6.18.30, 6.20 |
| Linux/Linuxgeneric | 7.0 | Not reported |
Published upstream
May 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.