CVE-2026-45946

published 27 May 2026 · updated 17 Nov 2026

power: supply: ab8500: Fix use-after-free in power_supply_changed()

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.14, Kernel 43cbb78ee047b9b12d096d40e3be265969d4c1f8, Kernel 46dbda27b028d78087667e8280966b99cec015ca and 11 more.

In the Linux kernel, the following vulnerability has been resolved: power: supply: ab8500: Fix use-after-free in power_supply_changed() Using the `devm_` variant for requesting IRQ _before_ the `devm_` variant for allocating/registering the `power_supply` handle, means that the `power_supply` handle will be deallocated/unregistered _before_ the interrupt handler (since `devm_` naturally deallocates in reverse allocation order). This means that during removal, there is a race condition where an interrupt can fire just _after_ the `power_supply` handle has been freed, *but* just _before_ the corresponding unregistration of the IRQ handler has run. This will lead to the IRQ handler calling `power_supply_changed()` with a freed `power_supply` handle. Which usually crashes the system or otherwise silently corrupts the memory... Note that there is a similar situation which can also happen during `probe()`; the possibility of an interrupt firing _before_ registering the `power_supply` handle. This would then lead to the nasty situation of using the `power_supply` handle *uninitialized* in `power_supply_changed()`. Commit 1c1f13a006ed ("power: supply: ab8500: Move to componentized binding") introduced this issue during a refactorization. Fix this racy use-after-free by making sure the IRQ is requested _after_ the registration of the `power_supply` handle.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=5.13.4 <5.14, >=1c1f13a006ed0d71bb5664c8b7e3e77a28da3beb <43cbb78ee047b9b12d096d40e3be265969d4c1f8, >=1c1f13a006ed0d71bb5664c8b7e3e77a28da3beb <46dbda27b028d78087667e8280966b99cec015ca, >=1c1f13a006ed0d71bb5664c8b7e3e77a28da3beb <551672981fe227122258a25a385a05f5c0746ad6, >=1c1f13a006ed0d71bb5664c8b7e3e77a28da3beb <709db4b476e254579d9c48ec34d397a41ca0c407, >=1c1f13a006ed0d71bb5664c8b7e3e77a28da3beb <847eeb6c0efcd76c7def73857cf798a4fcd8f79b, >=1c1f13a006ed0d71bb5664c8b7e3e77a28da3beb <c4af8a98bb52825a5331ae1d0604c0ea6956ba4b, >=1c1f13a006ed0d71bb5664c8b7e3e77a28da3beb <f50433f2603def08b21a4bf2fd238687fb5cbde9, =341db343768bc44f3512facc464021730d64071c, =5.145.14, 43cbb78ee047b9b12d096d40e3be265969d4c1f8, 46dbda27b028d78087667e8280966b99cec015ca, 551672981fe227122258a25a385a05f5c0746ad6, 709db4b476e254579d9c48ec34d397a41ca0c407, 847eeb6c0efcd76c7def73857cf798a4fcd8f79b, c4af8a98bb52825a5331ae1d0604c0ea6956ba4b, f50433f2603def08b21a4bf2fd238687fb5cbde9
linux-kernel: Kernel>=5.14.0 <5.15.202, >=5.16.0 <6.1.165, >=6.13.0 <6.18.14, >=6.19.0 <6.19.4, >=6.2.0 <6.6.128, >=6.7.0 <6.12.75, >=5.13.4 <5.145.15.202, 6.1.165, 6.18.14, 6.19.4, 6.6.128, 6.12.75, 5.14

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-45946 severity on Zeptric[![CVE-2026-45946](https://zeptric.io/badge/cve/CVE-2026-45946.svg)](https://zeptric.io/cve/CVE-2026-45946)