power: supply: sbs-battery: Fix use-after-free in power_supply_changed()
Summary
| CVE | CVE-2026-45916 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-05-27 14:17:06 UTC |
| Updated | 2026-05-27 14:48:03 UTC |
| Description | 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. |
Risk And Classification
EPSS: 0.000240000 probability, percentile 0.073320000 (date 2026-06-01)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected d2cec82c28802da31596b395ad292cb8f132fd63 ca7dd71773e4e050b0fb98768b7eae60f8d1f38b git | Not specified |
| CNA | Linux | Linux | affected d2cec82c28802da31596b395ad292cb8f132fd63 f1f472b14ad56104ba228b8fbec60d5b21829913 git | Not specified |
| CNA | Linux | Linux | affected d2cec82c28802da31596b395ad292cb8f132fd63 8010b745b436c3e1ca5dd960aa29fa3e0f6d8841 git | Not specified |
| CNA | Linux | Linux | affected d2cec82c28802da31596b395ad292cb8f132fd63 2078830c32d1e49ac942c6f8c21f35c806ae5e94 git | Not specified |
| CNA | Linux | Linux | affected d2cec82c28802da31596b395ad292cb8f132fd63 82d3eb97a976c9d56bb92b241397610e57a9c629 git | Not specified |
| CNA | Linux | Linux | affected d2cec82c28802da31596b395ad292cb8f132fd63 861dda7a9074c0ff67788928165ae39d7f647491 git | Not specified |
| CNA | Linux | Linux | affected d2cec82c28802da31596b395ad292cb8f132fd63 14d4dee5d8fb361bfff275832087254beab66d72 git | Not specified |
| CNA | Linux | Linux | affected d2cec82c28802da31596b395ad292cb8f132fd63 8d59cf3887fbabacef53bfba473e33e8a8d9d07b git | Not specified |
| CNA | Linux | Linux | affected 4.9 | Not specified |
| CNA | Linux | Linux | unaffected 4.9 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.252 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.202 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.165 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.128 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.75 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.14 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.19.4 6.19.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/8d59cf3887fbabacef53bfba473e33e8a8d9d07b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/2078830c32d1e49ac942c6f8c21f35c806ae5e94 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/f1f472b14ad56104ba228b8fbec60d5b21829913 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/82d3eb97a976c9d56bb92b241397610e57a9c629 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/8010b745b436c3e1ca5dd960aa29fa3e0f6d8841 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/861dda7a9074c0ff67788928165ae39d7f647491 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ca7dd71773e4e050b0fb98768b7eae60f8d1f38b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/14d4dee5d8fb361bfff275832087254beab66d72 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.