Skip to main content
VulnerabilityPublished Updated

CVE-2026-72182: Linux kernel · power: supply: charger-manager: fix refcount leak in is_full_charged()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in e8631b883338ea4c3b5d8ddfbe16407af9f0b4b9 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:04 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in e8631b883338ea4c3b5d8ddfbe16407af9f0b4b9, e44ad91e9f75f3e3ccbdb85ffe699471f9675e5b, afe3202c30bdff0635818ab525fe2694309d2692 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e132fc6bb89bd307cfcdb8ba24afcd1985261485, < e8631b883338ea4c3b5d8ddfbe16407af9f0b4b9
Fixed in
  • e8631b883338ea4c3b5d8ddfbe16407af9f0b4b9
LinuxLinuxAffected
  • ≥ e132fc6bb89bd307cfcdb8ba24afcd1985261485, < e44ad91e9f75f3e3ccbdb85ffe699471f9675e5b
Fixed in
  • e44ad91e9f75f3e3ccbdb85ffe699471f9675e5b
LinuxLinuxAffected
  • ≥ e132fc6bb89bd307cfcdb8ba24afcd1985261485, < afe3202c30bdff0635818ab525fe2694309d2692
Fixed in
  • afe3202c30bdff0635818ab525fe2694309d2692
LinuxLinuxAffected
  • ≥ e132fc6bb89bd307cfcdb8ba24afcd1985261485, < 4373cfa38ead58f980362c841b0d0bdf8c4d956c
Fixed in
  • 4373cfa38ead58f980362c841b0d0bdf8c4d956c
LinuxLinuxAffected
  • ≥ e132fc6bb89bd307cfcdb8ba24afcd1985261485, < 3999f47e4bbf864e3c7fbfd813fb2f651e6b5714
Fixed in
  • 3999f47e4bbf864e3c7fbfd813fb2f651e6b5714
LinuxLinuxAffected
  • ≥ e132fc6bb89bd307cfcdb8ba24afcd1985261485, < 193e6471e985c2f25d09b3fe96ec52f4eab89bd4
Fixed in
  • 193e6471e985c2f25d09b3fe96ec52f4eab89bd4

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.

References

Community reviews

Loading reviews…