Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected e132fc6bb89bd307cfcdb8ba24afcd1985261485 – < afe3202c30bdff0635818ab525fe2694309d2692
    • affected e132fc6bb89bd307cfcdb8ba24afcd1985261485 – < 93b99b63ad5657225faf702670ddfeddf1f0ae29
    • affected e132fc6bb89bd307cfcdb8ba24afcd1985261485 – < 6f75912cc6ff4c05ff13af351c4eea49b6b3c078
    • affected e132fc6bb89bd307cfcdb8ba24afcd1985261485 – < e44ad91e9f75f3e3ccbdb85ffe699471f9675e5b
    • affected e132fc6bb89bd307cfcdb8ba24afcd1985261485 – < 3999f47e4bbf864e3c7fbfd813fb2f651e6b5714
    • affected e132fc6bb89bd307cfcdb8ba24afcd1985261485 – < 193e6471e985c2f25d09b3fe96ec52f4eab89bd4
    • affected e132fc6bb89bd307cfcdb8ba24afcd1985261485 – < e8631b883338ea4c3b5d8ddfbe16407af9f0b4b9
    • affected e132fc6bb89bd307cfcdb8ba24afcd1985261485 – < 4373cfa38ead58f980362c841b0d0bdf8c4d956c
  • Linux · Linux

    • affected 5.10
    • unaffected < 5.10
    • unaffected 5.10.261 – ≤ 5.10.*
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-72182 badge
[![CVE-2026-72182](https://cveledger.app/badge/CVE-2026-72182.svg)](https://cveledger.app/cve/CVE-2026-72182)

Record last updated .