CVE-2026-45875

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
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:

mfd: arizona: Fix regulator resource leak on wm5102_clear_write_sequencer() failure

The wm5102_clear_write_sequencer() helper may return an error and just return, bypassing the cleanup sequence and causing regulators to remain enabled, leading to a resource leak.

Change the direct return to jump to the err_reset label to properly free the resources.

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
6%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 25, 2026

Advisory Details (8)

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

mfd: arizona: Fix regulator resource leak on wm5102_clear_write_sequencer() failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

mfd: arizona: Fix regulator resource leak on wm5102_clear_write_sequencer() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/933c5463873582baaecf5c38401ec4095b1c6269
generic

mfd: arizona: Fix regulator resource leak on wm5102_clear_write_sequencer() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5a4923726a165593d7601834a6fb2a10ab47b85d
generic

mfd: arizona: Fix regulator resource leak on wm5102_clear_write_sequencer() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/54eafc1b0dbcf79c5f8b6dc8d9e92e56b9384c0a
generic

mfd: arizona: Fix regulator resource leak on wm5102_clear_write_sequencer() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4feb753ba6e5e5bbaba868b841a2db41c21e56fa
generic

mfd: arizona: Fix regulator resource leak on wm5102_clear_write_sequencer() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/445cec7b4fbb1546836ae8e332d158e8d37d0fb6
generic

mfd: arizona: Fix regulator resource leak on wm5102_clear_write_sequencer() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3ea01691738b0decb63ea2705d2cdf27f6f26fc0
generic

mfd: arizona: Fix regulator resource leak on wm5102_clear_write_sequencer() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2049820d1e635e467d795237fd40287213d92349

Vendor Advisories for CVE-2026-45875(1)

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

Patch Availability(24)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-09-14ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-09-14ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-09-14ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-09-14ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-09-14ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-09-14ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-09-14ubuntu
linuxKernel @ 5.10.252—osv

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (103 versions)6.18.14-1—

Weakness Classification(1)

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

All Vendor Advisories

(23)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 37× 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 201 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45875?
CVE-2026-45875 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: mfd: arizona: Fix regulator resource leak on wm5102clearwrite_sequencer() failure The wm5102clearwrite_sequencer() helper may return an error and just return, bypassing the cleanup sequence and causing regulators to remain enabled,…
When was CVE-2026-45875 disclosed?
CVE-2026-45875 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45875 actively exploited?
CVE-2026-45875 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 93.8% of all scored CVEs.
What is the CVSS score of CVE-2026-45875?
CVE-2026-45875 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-45875?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45875, 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-45875

Explore →

Is Your Infrastructure Affected by CVE-2026-45875?

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

Start Free Scan →Browse All CVEs