CVE-2026-89472 (GCVE-0-2026-89472)
Vulnerability from cvelistv5 – Published: 2026-09-11 19:43 – Updated: 2026-10-30 12:31
VLAI
EPSS
VEX
Title
power: supply: charger-manager: register regulators before exposing sysfs
Summary
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.
Severity
7.8 (High)
Assigner
References
6 references
Impacted products
2 products
| Vendor | Product | Version | |
|---|---|---|---|
| Linux | Linux |
Affected:
3950c7865cd7c963982a2c94457182b96732f4c9 , < 5763750916d28a29f1375a14dd6dadd5f2d2e178
(git)
Affected: 3950c7865cd7c963982a2c94457182b96732f4c9 , < 6e1645a6ee85d070c2d8dd847f1ce110dc2455c1 (git) Affected: 3950c7865cd7c963982a2c94457182b96732f4c9 , < af3ce383ba0d0d48957a22ac7058ff5698775898 (git) Affected: 3950c7865cd7c963982a2c94457182b96732f4c9 , < 86e4fa65368f3bbb506dddba8c9eedc75bd603b2 (git) Affected: 3950c7865cd7c963982a2c94457182b96732f4c9 , < 6d532582ff3c420598f02945b13184c738cc1581 (git) Affected: 3950c7865cd7c963982a2c94457182b96732f4c9 , < c57cb36f76eb7ced45f57af1a890d8f3a6d76342 (git) |
|
| Linux | Linux |
Affected:
3.7
Unaffected: 0 , < 3.7 (semver) Unaffected: 6.1.191 , ≤ 6.1.* (semver) Unaffected: 6.6.160 , ≤ 6.6.* (semver) Unaffected: 6.12.109 , ≤ 6.12.* (semver) Unaffected: 6.18.50 , ≤ 6.18.* (semver) Unaffected: 7.2.4 , ≤ 7.2.* (semver) Unaffected: 7.3 , ≤ * (original_commit_for_fix) |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/power/supply/charger-manager.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "5763750916d28a29f1375a14dd6dadd5f2d2e178",
"status": "affected",
"version": "3950c7865cd7c963982a2c94457182b96732f4c9",
"versionType": "git"
},
{
"lessThan": "6e1645a6ee85d070c2d8dd847f1ce110dc2455c1",
"status": "affected",
"version": "3950c7865cd7c963982a2c94457182b96732f4c9",
"versionType": "git"
},
{
"lessThan": "af3ce383ba0d0d48957a22ac7058ff5698775898",
"status": "affected",
"version": "3950c7865cd7c963982a2c94457182b96732f4c9",
"versionType": "git"
},
{
"lessThan": "86e4fa65368f3bbb506dddba8c9eedc75bd603b2",
"status": "affected",
"version": "3950c7865cd7c963982a2c94457182b96732f4c9",
"versionType": "git"
},
{
"lessThan": "6d532582ff3c420598f02945b13184c738cc1581",
"status": "affected",
"version": "3950c7865cd7c963982a2c94457182b96732f4c9",
"versionType": "git"
},
{
"lessThan": "c57cb36f76eb7ced45f57af1a890d8f3a6d76342",
"status": "affected",
"version": "3950c7865cd7c963982a2c94457182b96732f4c9",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/power/supply/charger-manager.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "3.7"
},
{
"lessThan": "3.7",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.191",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.160",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.109",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.50",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.191",
"versionStartIncluding": "3.7",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.160",
"versionStartIncluding": "3.7",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.109",
"versionStartIncluding": "3.7",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.50",
"versionStartIncluding": "3.7",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2.4",
"versionStartIncluding": "3.7",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.3",
"versionStartIncluding": "3.7",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\npower: supply: charger-manager: register regulators before exposing sysfs\n\ncharger_manager_remove() and the err_reg_extcon probe error path free each\ncharger regulator with regulator_put() before tearing down the power_supply\nsysfs entries (power_supply_unregister()). charger_manager_remove() also\ncalls try_charger_enable(cm, false) after the regulator_put() loop. A\nconcurrent write to a charger\u0027s externally_control sysfs attribute that\nlands between regulator_put() and power_supply_unregister() can run\ncharger_externally_control_store() and call try_charger_enable(), which,\nwhen charging is enabled, dereferences the already-freed consumer handle.\nWhen charging is enabled, try_charger_enable(cm, false) in .remove() also\ndereferences the freed handles directly. Both leave use-after-free windows.\nSymmetrically, probe registers the sysfs entries (power_supply_register)\nbefore acquiring the regulators (regulator_get, inside\ncharger_manager_register_extcon), so userspace can reach externally_control\nbefore the regulators are available.\n\nSplit charger_manager_register_extcon() on the sync/async boundary:\ncharger_manager_get_regulators() (regulator_get only, no async producer)\nnow runs before power_supply_register() so sysfs is not live before\nregulators are available, and charger_manager_register_extcon() keeps only\nthe extcon notifier/work setup, still after power_supply_register() so a\npower_supply_register() failure cannot reach extcon setup. This keeps the\nsysfs setup/teardown ordering symmetric without introducing an asynchronous\nproducer on the earlier probe-error path.\n\nMove power_supply_unregister() and try_charger_enable(cm, false) ahead of\nthe regulator_put() loop on both teardown paths, and adjust err_reg_extcon\n(power_supply_unregister() then fall through err_regulator for\nregulator_put(); get_regulators self-rolls back on its own failure).\n\nThis does not address the separate extcon-notifier-driven deref of the same\nhandles, which needs its own synchronization design.\n\nFound by an in-house static analysis tool."
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - The UAF is reached via local sysfs under /sys/class/power_supply/*/charger.N/{state,externally_control} and via charger_manager_remove()/probe unwind on the charger-manager platform device; this power-supply driver has no network, Bluetooth, or remote packet path into try_charger_enable() or the sysfs handlers.\nAC:L - An attacker can hammer the live sysfs attributes while teardown or probe unwind runs, controlling the sysfs side of the race; charger_manager_remove() also deterministically calls try_charger_enable() on already-freed regulator consumers when charging is enabled, with no attacker-uncontrollable memory layout required.\nPR:L - charger.N/state is mode 0444 and charger_state_show() calls regulator_is_enabled() on the consumer, so an unprivileged local user (including apps on charger-manager phones/embedded devices) can hit the UAF during the teardown or probe window; per driver-removal UAF precedent this is PR:L even though sysfs unbind itself is privileged.\nUI:N - The attacker performs their own sysfs reads or writes against the charger-manager power_supply attributes and can race driver unbind or probe; no separate victim action such as mounting a filesystem or confirming a prompt is required.\nS:U - The dangling struct regulator is kernel heap used by the same host kernel; this is a standard in-kernel use-after-free/privilege-escalation within one security authority, not a VM escape, IOMMU bypass, or sandbox breakout.\nC:H - regulator_put() kfree()s the struct regulator while charger_state_show() and try_charger_enable() still dereference the consumer; this heap UAF lets a reused object be read through regulator_is_enabled() and related helpers, enabling arbitrary kernel information disclosure.\nI:H - The same dangling consumer is passed to regulator_enable(), regulator_disable(), and regulator_force_disable() from try_charger_enable() and charger_externally_control_store(), so a sprayed heap object can turn the UAF into arbitrary writes and control-flow hijack.\nA:H - Use of the freed or still-NULL regulator consumer oopses or panics the kernel in regulator_is_enabled()/enable()/disable(), and the UAF crashes even when it is not fully converted into a read/write primitive."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-30T12:31:50.628Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/5763750916d28a29f1375a14dd6dadd5f2d2e178"
},
{
"url": "https://git.kernel.org/stable/c/6e1645a6ee85d070c2d8dd847f1ce110dc2455c1"
},
{
"url": "https://git.kernel.org/stable/c/af3ce383ba0d0d48957a22ac7058ff5698775898"
},
{
"url": "https://git.kernel.org/stable/c/86e4fa65368f3bbb506dddba8c9eedc75bd603b2"
},
{
"url": "https://git.kernel.org/stable/c/6d532582ff3c420598f02945b13184c738cc1581"
},
{
"url": "https://git.kernel.org/stable/c/c57cb36f76eb7ced45f57af1a890d8f3a6d76342"
}
],
"title": "power: supply: charger-manager: register regulators before exposing sysfs",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-89472",
"datePublished": "2026-09-11T19:43:30.536Z",
"dateReserved": "2026-09-11T19:38:34.710Z",
"dateUpdated": "2026-10-30T12:31:50.628Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-89472",
"date": "2026-11-17",
"epss": "0.0017",
"percentile": "0.06451"
},
"microsoft_vex": {
"current_release_date": "2026-11-07T01:48:31.000Z",
"cve": "CVE-2026-89472",
"id": "msrc_CVE-2026-89472",
"initial_release_date": "2026-10-23T01:13:41.000Z",
"product_status:fixed": "1",
"product_status:known_affected": "2",
"source": "Microsoft CSAF VEX",
"status": "final",
"title": "power: supply: charger-manager: register regulators before exposing sysfs",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-89472.json",
"version": "4"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/power/supply/charger-manager.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "5763750916d28a29f1375a14dd6dadd5f2d2e178",
"status": "affected",
"version": "3950c7865cd7c963982a2c94457182b96732f4c9",
"versionType": "git"
},
{
"lessThan": "6e1645a6ee85d070c2d8dd847f1ce110dc2455c1",
"status": "affected",
"version": "3950c7865cd7c963982a2c94457182b96732f4c9",
"versionType": "git"
},
{
"lessThan": "af3ce383ba0d0d48957a22ac7058ff5698775898",
"status": "affected",
"version": "3950c7865cd7c963982a2c94457182b96732f4c9",
"versionType": "git"
},
{
"lessThan": "86e4fa65368f3bbb506dddba8c9eedc75bd603b2",
"status": "affected",
"version": "3950c7865cd7c963982a2c94457182b96732f4c9",
"versionType": "git"
},
{
"lessThan": "6d532582ff3c420598f02945b13184c738cc1581",
"status": "affected",
"version": "3950c7865cd7c963982a2c94457182b96732f4c9",
"versionType": "git"
},
{
"lessThan": "c57cb36f76eb7ced45f57af1a890d8f3a6d76342",
"status": "affected",
"version": "3950c7865cd7c963982a2c94457182b96732f4c9",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/power/supply/charger-manager.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "3.7"
},
{
"lessThan": "3.7",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.191",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.160",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.109",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.50",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\npower: supply: charger-manager: register regulators before exposing sysfs\n\ncharger_manager_remove() and the err_reg_extcon probe error path free each\ncharger regulator with regulator_put() before tearing down the power_supply\nsysfs entries (power_supply_unregister()). charger_manager_remove() also\ncalls try_charger_enable(cm, false) after the regulator_put() loop. A\nconcurrent write to a charger\u0027s externally_control sysfs attribute that\nlands between regulator_put() and power_supply_unregister() can run\ncharger_externally_control_store() and call try_charger_enable(), which,\nwhen charging is enabled, dereferences the already-freed consumer handle.\nWhen charging is enabled, try_charger_enable(cm, false) in .remove() also\ndereferences the freed handles directly. Both leave use-after-free windows.\nSymmetrically, probe registers the sysfs entries (power_supply_register)\nbefore acquiring the regulators (regulator_get, inside\ncharger_manager_register_extcon), so userspace can reach externally_control\nbefore the regulators are available.\n\nSplit charger_manager_register_extcon() on the sync/async boundary:\ncharger_manager_get_regulators() (regulator_get only, no async producer)\nnow runs before power_supply_register() so sysfs is not live before\nregulators are available, and charger_manager_register_extcon() keeps only\nthe extcon notifier/work setup, still after power_supply_register() so a\npower_supply_register() failure cannot reach extcon setup. This keeps the\nsysfs setup/teardown ordering symmetric without introducing an asynchronous\nproducer on the earlier probe-error path.\n\nMove power_supply_unregister() and try_charger_enable(cm, false) ahead of\nthe regulator_put() loop on both teardown paths, and adjust err_reg_extcon\n(power_supply_unregister() then fall through err_regulator for\nregulator_put(); get_regulators self-rolls back on its own failure).\n\nThis does not address the separate extcon-notifier-driven deref of the same\nhandles, which needs its own synchronization design.\n\nFound by an in-house static analysis tool."
}
],
"id": "CVE-2026-89472",
"lastModified": "2026-10-30T13:20:17.203",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
]
},
"published": "2026-09-11T20:19:28.393",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/5763750916d28a29f1375a14dd6dadd5f2d2e178"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/6d532582ff3c420598f02945b13184c738cc1581"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/6e1645a6ee85d070c2d8dd847f1ce110dc2455c1"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/86e4fa65368f3bbb506dddba8c9eedc75bd603b2"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/af3ce383ba0d0d48957a22ac7058ff5698775898"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c57cb36f76eb7ced45f57af1a890d8f3a6d76342"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-06T01:15:42+00:00",
"cve": "CVE-2026-89472",
"id": "CVE-2026-89472",
"initial_release_date": "2026-09-11T00:00:00+00:00",
"product_status:known_affected": "1",
"product_status:known_not_affected": "202",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: power: supply: charger-manager: register regulators before exposing sysfs",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-89472.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-11-14T01:41:47Z",
"cve": "CVE-2026-89472",
"id": "CVE-2026-89472",
"initial_release_date": "2026-09-12T16:27:54Z",
"product_status:known_affected": "211",
"product_status:known_not_affected": "145",
"product_status:recommended": "237",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-89472",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-89472.json",
"version": "11"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…