Regulator resource leak via skipped failure cleanup
Published May 27, 2026 · Updated May 27, 2026
Resource leakage in the Arizona MFD driver in Linux Kernel leaves regulators enabled after a hardware/I2C initialization error. wm5102_clear_write_sequencer() returns directly on failure instead of jumping to err_reset, bypassing regulator-disable and reset cleanup. The required hardware/I2C error occurs during device initialization and cannot be invoked or influenced by attackers.
Summary
What happened
Resource leakage in the Arizona MFD driver in Linux Kernel leaves regulators enabled after a hardware/I2C initialization error. wm5102_clear_write_sequencer() returns directly on failure instead of jumping to err_reset, bypassing regulator-disable and reset cleanup. The required hardware/I2C error occurs during device initialization and cannot be invoked or influenced by attackers.
The record
- CVE
- CVE-2026-45875
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 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=1c1c6bba57f51331f64f32d0ce9a0f9883041205 <2049820d1e635e467d795237fd40287213d92349
- Affected versionversion=1c1c6bba57f51331f64f32d0ce9a0f9883041205 <3ea01691738b0decb63ea2705d2cdf27f6f26fc0
- Affected versionversion=1c1c6bba57f51331f64f32d0ce9a0f9883041205 <445cec7b4fbb1546836ae8e332d158e8d37d0fb6
- Affected versionversion=1c1c6bba57f51331f64f32d0ce9a0f9883041205 <4feb753ba6e5e5bbaba868b841a2db41c21e56fa
- Affected versionversion=1c1c6bba57f51331f64f32d0ce9a0f9883041205 <54eafc1b0dbcf79c5f8b6dc8d9e92e56b9384c0a
- Affected versionversion=1c1c6bba57f51331f64f32d0ce9a0f9883041205 <5a4923726a165593d7601834a6fb2a10ab47b85d
- Affected versionversion=1c1c6bba57f51331f64f32d0ce9a0f9883041205 <933c5463873582baaecf5c38401ec4095b1c6269
- Affected versionversion=1c1c6bba57f51331f64f32d0ce9a0f9883041205 <e0527c09bcf1e6beeb685a7f4177683866b8609c
- Affected versionversion=4.2
What conditions does exploitation require?
What is affected?
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
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