CVE-2026-45916
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| debian | bookworm | fixed | 6.1.170-1 |
| debian | forky | fixed | 6.18.14-1 |
| debian | sid | fixed | 6.18.14-1 |
| debian | trixie | fixed | 6.12.85-1 |
| sles | affected | | |
| debian | bullseye | fixed | 5.10.257-1 |
References
- https://git.kernel.org/stable/c/ca7dd71773e4e050b0fb98768b7eae60f8d1f38b
- https://git.kernel.org/stable/c/f1f472b14ad56104ba228b8fbec60d5b21829913
- https://git.kernel.org/stable/c/8010b745b436c3e1ca5dd960aa29fa3e0f6d8841
- https://git.kernel.org/stable/c/2078830c32d1e49ac942c6f8c21f35c806ae5e94
- https://git.kernel.org/stable/c/82d3eb97a976c9d56bb92b241397610e57a9c629
- https://git.kernel.org/stable/c/861dda7a9074c0ff67788928165ae39d7f647491
- https://git.kernel.org/stable/c/14d4dee5d8fb361bfff275832087254beab66d72
- https://git.kernel.org/stable/c/8d59cf3887fbabacef53bfba473e33e8a8d9d07b
- https://security-tracker.debian.org/tracker/CVE-2026-45916
- https://www.suse.com/security/cve/CVE-2026-45916.html
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.