CVE-2026-99444
power: supply: sbs-battery: disable polling before supply teardown
What happened?
In the Linux kernel, the following vulnerability has been resolved:
power: supply: sbs-battery: disable polling before supply teardown
The managed poll-work cancellation is registered before the power supply, so cleanup unregisters the supply before draining polling. A pending or running poller can then call power_supply_changed() on the released supply.
Commit 8d59cf3887fb ("power: supply: sbs-battery: Fix use-after-free in power_supply_changed()") moved the IRQ request after supply registration, but did not change the poll-work cancellation order.
Add a later managed action that disables and drains polling before supply teardown. Its retained disabled state prevents external-power callbacks from rearming the poll work after it has been drained. Keep the original autocancel to initialize work before supply callbacks can run and to cover failed supply registration.
The teardown ordering issue was found by static analysis.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: 6d0c5de2fd84a0ad07f0cecea24def3987675192 to < 3146e37745171f9b9b8aab48d9b8dbcb14a186e0; affected: 6d0c5de2fd84a0ad07f0cecea24def3987675192 to < fce1dd31b185ceadb9669162a5a35444b1059960; affected: 6d0c5de2fd84a0ad07f0cecea24def3987675192 to < 190a92be785336a03c36450af560a79a631b192d; affected: 6d0c5de2fd84a0ad07f0cecea24def3987675192 to < 5c1c602463d597c5189ddc5a73dece588ba2c57a | See vendor advisory |
| LinuxLinux | affected: 5.13; unaffected: 0 to < 5.13; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99444
- https://git.kernel.org/stable/c/3146e37745171f9b9b8aab48d9b8dbcb14a186e0
- https://git.kernel.org/stable/c/fce1dd31b185ceadb9669162a5a35444b1059960
- https://git.kernel.org/stable/c/190a92be785336a03c36450af560a79a631b192d
- https://git.kernel.org/stable/c/5c1c602463d597c5189ddc5a73dece588ba2c57a