PoC Monitor
← All CVEs
CVE-2026-89472published 11 Sep 2026 19:43 UTCData: JSON · API

Linux

power: supply: charger-manager: register regulators before exposing sysfs

In the Linux kernel, the following vulnerability has been resolved: power: supply: charger-manager: register regulators before exposing sysfs charger_manager_remove() and the err_reg_extcon probe error path free each charger regulator with regulator_put() before tearing down the power_supply sysfs entries (power_supply_unregister()). charger_manager_remove() also calls try_charger_enable(cm, false) after the regulator_put() loop. A concurrent write to a charger's externally_control sysfs attribute that lands between regulator_put() and power_supply_unregister() can run charger_externally_control_store() and call try_charger_enable(), which, when charging is enabled, dereferences the already-freed consumer handle. When charging is enabled, try_charger_enable(cm, false) in .remove() also dereferences the freed handles directly. Both leave use-after-free windows. Symmetrically, probe registers the sysfs entries (power_supply_register) before acquiring the regulators (regulator_get, inside charger_manager_register_extcon), so userspace can reach externally_control before the regulators are available. Split charger_manager_register_extcon() on the sync/async boundary: charger_manager_get_regulators() (regulator_get only, no async producer) now runs before power_supply_register() so sysfs is not live before regulators are available, and charger_manager_register_extcon() keeps only the extcon notifier/work setup, still after power_supply_register() so a power_supply_register() failure cannot reach extcon setup. This keeps the sysfs setup/teardown ordering symmetric without introducing an asynchronous producer on the earlier probe-error path. Move power_supply_unregister() and try_charger_enable(cm, false) ahead of the regulator_put() loop on both teardown paths, and adjust err_reg_extcon (power_supply_unregister() then fall through err_regulator for regulator_put(); get_regulators self-rolls back on its own failure). This does not address the separate extcon-notifier-driven deref of the same handles, which needs its own synchronization design. Found by an in-house static analysis tool.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 3950c7865cd7c963982a2c94457182b96732f4c9, < 5763750916d28a29f1375a14dd6dadd5f2d2e178
  • >= 3950c7865cd7c963982a2c94457182b96732f4c9, < 6e1645a6ee85d070c2d8dd847f1ce110dc2455c1
  • >= 3950c7865cd7c963982a2c94457182b96732f4c9, < af3ce383ba0d0d48957a22ac7058ff5698775898
  • >= 3950c7865cd7c963982a2c94457182b96732f4c9, < 86e4fa65368f3bbb506dddba8c9eedc75bd603b2
  • >= 3950c7865cd7c963982a2c94457182b96732f4c9, < 6d532582ff3c420598f02945b13184c738cc1581
  • >= 3950c7865cd7c963982a2c94457182b96732f4c9, < c57cb36f76eb7ced45f57af1a890d8f3a6d76342

Fixed in 5763750916d28a29f1375a14dd6dadd5f2d2e178, 6e1645a6ee85d070c2d8dd847f1ce110dc2455c1, af3ce383ba0d0d48957a22ac7058ff5698775898, 86e4fa65368f3bbb506dddba8c9eedc75bd603b2, 6d532582ff3c420598f02945b13184c738cc1581, c57cb36f76eb7ced45f57af1a890d8f3a6d76342

Linux Linux
  • 3.7

Fixed in 0, 6.1.191, 6.6.160, 6.12.109, 6.18.50, 7.2.4, 7.3

Mitigation

Upgrade Linux to 5763750916d28a29f1375a14dd6dadd5f2d2e178 or 6e1645a6ee85d070c2d8dd847f1ce110dc2455c1 or af3ce383ba0d0d48957a22ac7058ff5698775898 or 86e4fa65368f3bbb506dddba8c9eedc75bd603b2 or 6d532582ff3c420598f02945b13184c738cc1581 or c57cb36f76eb7ced45f57af1a890d8f3a6d76342 or later.

Upgrade Linux to 0 or 6.1.191 or 6.6.160 or 6.12.109 or 6.18.50 or 7.2.4 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published11 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.