power: supply: charger-manager: fix refcount leak in is_full_charged()
Summary
| CVE | CVE-2026-72182 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-15 06:21:36 UTC |
| Updated | 2026-08-17 06:18:18 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: power: supply: charger-manager: fix refcount leak in is_full_charged() In is_full_charged(), power_supply_get_by_name() is called to obtain a reference to the fuel_gauge power supply. If the voltage check (uV >= desc->fullbatt_uV) succeeds, the function returns true directly without releasing the reference, leaking the refcount. Fix this by setting a flag and jumping to the out label where power_supply_put() properly drops the reference. |
Risk And Classification
EPSS: 0.002100000 probability, percentile 0.115380000 (date 2026-08-17)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected e132fc6bb89bd307cfcdb8ba24afcd1985261485 afe3202c30bdff0635818ab525fe2694309d2692 git | Not specified |
| CNA | Linux | Linux | affected e132fc6bb89bd307cfcdb8ba24afcd1985261485 93b99b63ad5657225faf702670ddfeddf1f0ae29 git | Not specified |
| CNA | Linux | Linux | affected e132fc6bb89bd307cfcdb8ba24afcd1985261485 6f75912cc6ff4c05ff13af351c4eea49b6b3c078 git | Not specified |
| CNA | Linux | Linux | affected e132fc6bb89bd307cfcdb8ba24afcd1985261485 e44ad91e9f75f3e3ccbdb85ffe699471f9675e5b git | Not specified |
| CNA | Linux | Linux | affected e132fc6bb89bd307cfcdb8ba24afcd1985261485 3999f47e4bbf864e3c7fbfd813fb2f651e6b5714 git | Not specified |
| CNA | Linux | Linux | affected e132fc6bb89bd307cfcdb8ba24afcd1985261485 193e6471e985c2f25d09b3fe96ec52f4eab89bd4 git | Not specified |
| CNA | Linux | Linux | affected e132fc6bb89bd307cfcdb8ba24afcd1985261485 e8631b883338ea4c3b5d8ddfbe16407af9f0b4b9 git | Not specified |
| CNA | Linux | Linux | affected e132fc6bb89bd307cfcdb8ba24afcd1985261485 4373cfa38ead58f980362c841b0d0bdf8c4d956c git | Not specified |
| CNA | Linux | Linux | affected 5.10 | Not specified |
| CNA | Linux | Linux | unaffected 5.10 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.261 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.212 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.178 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.145 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.97 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.40 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.5 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/193e6471e985c2f25d09b3fe96ec52f4eab89bd4 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/3999f47e4bbf864e3c7fbfd813fb2f651e6b5714 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/4373cfa38ead58f980362c841b0d0bdf8c4d956c | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/6f75912cc6ff4c05ff13af351c4eea49b6b3c078 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/afe3202c30bdff0635818ab525fe2694309d2692 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/93b99b63ad5657225faf702670ddfeddf1f0ae29 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/e8631b883338ea4c3b5d8ddfbe16407af9f0b4b9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/e44ad91e9f75f3e3ccbdb85ffe699471f9675e5b | 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.