CVE-2026-46109

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-28. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 24, 2026

Advisory Details (8)

Auto-updated Jun 24, 2026
No patch confirmed yet.
generic

usb: ulpi: fix memory leak on ulpi_register() error paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f30ccfc2985590b33a23a3d8bed7ca16c0af551b
generic

usb: ulpi: fix memory leak on ulpi_register() error paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f1b855c00988a9cb41134cab7cf9faedba775dd9
generic

usb: ulpi: fix memory leak on ulpi_register() error paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/be2c1d825f54277472c87019e82013ac534ddc4c
generic

usb: ulpi: fix memory leak on ulpi_register() error paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b0c0d44adb55c66663886cb6e30ee92cbb0f5385
generic

usb: ulpi: fix memory leak on ulpi_register() error paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7bd61ed0bf9f4f1f2673d489b3bda1555b48d054
generic

usb: ulpi: fix memory leak on ulpi_register() error paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2a71e01b2cf9b4329ff67102c1bea7448c2a2d2d
generic

usb: ulpi: fix memory leak on ulpi_register() error paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0c2c0c6820fe96fa4be0a0499f8d3f3321b9af6c
generic

usb: ulpi: fix memory leak on ulpi_register() error paths - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b9fcab1b8608d429e5f239afb197de928d4de7d

Vendor Advisories for CVE-2026-46109(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.88-1~bpo12+1 (21 versions)6.12.88-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (133 versions)7.0.7-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(8)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 68× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 213 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 04:58 UTCEG score recompute
  11. 2026-08-25 04:58 UTCVendor advisory
  12. 2026-08-25 04:58 UTCGHSA enrichment
  13. 2026-08-23 14:49 UTCEG score recompute
  14. 2026-08-23 14:49 UTCVendor advisory
  15. 2026-08-23 14:48 UTCGHSA enrichment
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-21 23:49 UTCEPSS rescore
  18. 2026-08-21 15:55 UTCEG score recompute
  19. 2026-08-21 15:55 UTCVendor advisory
  20. 2026-08-21 15:55 UTCGHSA enrichment
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-20 11:09 UTCEG score recompute
  23. 2026-08-20 11:09 UTCVendor advisory
  24. 2026-08-20 11:09 UTCGHSA enrichment
  25. 2026-08-19 17:04 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 09:01 UTCEG score recompute
  4. 2026-08-17 09:01 UTCVendor advisory
  5. 2026-08-17 09:01 UTCGHSA enrichment
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 02:41 UTCEG score recompute
  8. 2026-08-16 02:41 UTCVendor advisory
  9. 2026-08-16 02:41 UTCGHSA enrichment
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-15 00:18 UTCVendor advisory
  13. 2026-08-15 00:18 UTCGHSA enrichment
  14. 2026-08-14 01:21 UTCEG score recompute
  15. 2026-08-14 01:21 UTCVendor advisory
  16. 2026-08-14 01:21 UTCGHSA enrichment
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-12 22:01 UTCEG score recompute
  19. 2026-08-12 22:01 UTCVendor advisory
  20. 2026-08-12 22:01 UTCGHSA enrichment
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-11 23:04 UTCEG score recompute
  23. 2026-08-11 23:04 UTCVendor advisory
  24. 2026-08-11 23:04 UTCGHSA enrichment
  25. 2026-08-11 00:08 UTCEG score recompute
  26. 2026-08-11 00:08 UTCVendor advisory
  27. 2026-08-11 00:07 UTCGHSA enrichment
  28. 2026-08-11 00:00 UTCEPSS rescore
  29. 2026-08-09 17:35 UTCEG score recompute
  30. 2026-08-09 17:35 UTCVendor advisory
  31. 2026-08-09 17:35 UTCGHSA enrichment
  32. 2026-08-09 13:46 UTCEPSS rescore
  33. 2026-08-08 18:39 UTCEG score recompute
  34. 2026-08-08 18:39 UTCVendor advisory
  35. 2026-08-08 18:39 UTCGHSA enrichment
  36. 2026-08-08 16:37 UTCEPSS rescore
  37. 2026-08-07 18:45 UTCEG score recompute
  38. 2026-08-07 18:45 UTCVendor advisory
  39. 2026-08-07 18:45 UTCGHSA enrichment
  40. 2026-08-06 19:46 UTCEG score recompute
  41. 2026-08-06 19:46 UTCVendor advisory
  42. 2026-08-06 19:46 UTCGHSA enrichment
  43. 2026-08-06 13:47 UTCEPSS rescore
  44. 2026-08-05 20:49 UTCEG score recompute
  45. 2026-08-05 20:49 UTCVendor advisory
  46. 2026-08-05 20:49 UTCGHSA enrichment
  47. 2026-08-05 19:17 UTCEPSS rescore
  48. 2026-08-04 15:10 UTCEPSS rescore
  49. 2026-08-04 10:39 UTCEPSS rescore
  50. 2026-08-03 16:16 UTCEG score recompute
  51. 2026-08-03 16:16 UTCVendor advisory
  52. 2026-08-03 16:16 UTCGHSA enrichment
  53. 2026-08-03 10:36 UTCEPSS rescore
  54. 2026-08-02 13:49 UTCEG score recompute
  55. 2026-08-02 13:49 UTCVendor advisory
  56. 2026-08-02 13:49 UTCGHSA enrichment
  57. 2026-08-02 02:27 UTCEPSS rescore
  58. 2026-08-01 14:52 UTCEG score recompute
  59. 2026-08-01 14:52 UTCVendor advisory
  60. 2026-08-01 14:52 UTCGHSA enrichment
  61. 2026-08-01 04:16 UTCEPSS rescore
  62. 2026-07-31 06:48 UTCEG score recompute
  63. 2026-07-31 06:48 UTCVendor advisory
  64. 2026-07-31 06:48 UTCGHSA enrichment
  65. 2026-07-30 16:28 UTCEPSS rescore
  66. 2026-07-30 01:30 UTCEPSS rescore
  67. 2026-07-29 14:34 UTCEG score recompute
  68. 2026-07-29 14:34 UTCVendor advisory
  69. 2026-07-29 14:34 UTCGHSA enrichment
  70. 2026-07-28 15:36 UTCEPSS rescore
  71. 2026-07-27 14:13 UTCEPSS rescore
  72. 2026-07-27 09:49 UTCEG score recompute
  73. 2026-07-27 09:49 UTCVendor advisory
  74. 2026-07-27 09:49 UTCGHSA enrichment
  75. 2026-07-26 14:54 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-46109?
CVE-2026-46109 is a medium vulnerability published on May 28, 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 ulpiregisterinterface() error path") removed kfree(ulpi) from ulpiregisterinterface() to fix a double-free when…
When was CVE-2026-46109 disclosed?
CVE-2026-46109 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46109 actively exploited?
CVE-2026-46109 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.7% of all scored CVEs.
What is the CVSS score of CVE-2026-46109?
CVE-2026-46109 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46109?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46109, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46109

Explore →

Is Your Infrastructure Affected by CVE-2026-46109?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs