CVE-2026-45916

published 27 May 2026 · updated 27 May 2026

power: supply: sbs-battery: 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 14d4dee5d8fb361bfff275832087254beab66d72, Kernel 2078830c32d1e49ac942c6f8c21f35c806ae5e94, Kernel 8010b745b436c3e1ca5dd960aa29fa3e0f6d8841 and 5 more.

In the Linux kernel, the following vulnerability has been resolved: power: supply: sbs-battery: 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()`. Fix this racy use-after-free by making sure the IRQ is requested _after_ the registration of the `power_supply` handle. Keep the old behavior of just printing a warning in case of any failures during the IRQ request and finishing the probe successfully.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=4.9, >=d2cec82c28802da31596b395ad292cb8f132fd63 <14d4dee5d8fb361bfff275832087254beab66d72, >=d2cec82c28802da31596b395ad292cb8f132fd63 <2078830c32d1e49ac942c6f8c21f35c806ae5e94, >=d2cec82c28802da31596b395ad292cb8f132fd63 <8010b745b436c3e1ca5dd960aa29fa3e0f6d8841, >=d2cec82c28802da31596b395ad292cb8f132fd63 <82d3eb97a976c9d56bb92b241397610e57a9c629, >=d2cec82c28802da31596b395ad292cb8f132fd63 <861dda7a9074c0ff67788928165ae39d7f647491, >=d2cec82c28802da31596b395ad292cb8f132fd63 <8d59cf3887fbabacef53bfba473e33e8a8d9d07b, >=d2cec82c28802da31596b395ad292cb8f132fd63 <ca7dd71773e4e050b0fb98768b7eae60f8d1f38b, >=d2cec82c28802da31596b395ad292cb8f132fd63 <f1f472b14ad56104ba228b8fbec60d5b2182991314d4dee5d8fb361bfff275832087254beab66d72, 2078830c32d1e49ac942c6f8c21f35c806ae5e94, 8010b745b436c3e1ca5dd960aa29fa3e0f6d8841, 82d3eb97a976c9d56bb92b241397610e57a9c629, 861dda7a9074c0ff67788928165ae39d7f647491, 8d59cf3887fbabacef53bfba473e33e8a8d9d07b, ca7dd71773e4e050b0fb98768b7eae60f8d1f38b, f1f472b14ad56104ba228b8fbec60d5b21829913

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-45916 severity on Zeptric[![CVE-2026-45916](https://zeptric.io/badge/cve/CVE-2026-45916.svg)](https://zeptric.io/cve/CVE-2026-45916)