From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72182: power: supply: charger-manager: fix refcount leak in is_full_charged()
Date: Sat, 15 Aug 2026 15:04:21 +0900 [thread overview]
Message-ID: <2026081540-CVE-2026-72182-39e5@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-72182 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.10 with commit e132fc6bb89bd307cfcdb8ba24afcd1985261485 and fixed in 5.10.261 with commit afe3202c30bdff0635818ab525fe2694309d2692
Issue introduced in 5.10 with commit e132fc6bb89bd307cfcdb8ba24afcd1985261485 and fixed in 5.15.212 with commit 93b99b63ad5657225faf702670ddfeddf1f0ae29
Issue introduced in 5.10 with commit e132fc6bb89bd307cfcdb8ba24afcd1985261485 and fixed in 6.1.178 with commit 6f75912cc6ff4c05ff13af351c4eea49b6b3c078
Issue introduced in 5.10 with commit e132fc6bb89bd307cfcdb8ba24afcd1985261485 and fixed in 6.6.145 with commit e44ad91e9f75f3e3ccbdb85ffe699471f9675e5b
Issue introduced in 5.10 with commit e132fc6bb89bd307cfcdb8ba24afcd1985261485 and fixed in 6.12.97 with commit 3999f47e4bbf864e3c7fbfd813fb2f651e6b5714
Issue introduced in 5.10 with commit e132fc6bb89bd307cfcdb8ba24afcd1985261485 and fixed in 6.18.40 with commit 193e6471e985c2f25d09b3fe96ec52f4eab89bd4
Issue introduced in 5.10 with commit e132fc6bb89bd307cfcdb8ba24afcd1985261485 and fixed in 7.1.5 with commit e8631b883338ea4c3b5d8ddfbe16407af9f0b4b9
Issue introduced in 5.10 with commit e132fc6bb89bd307cfcdb8ba24afcd1985261485 and fixed in 7.2-rc1 with commit 4373cfa38ead58f980362c841b0d0bdf8c4d956c
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-72182
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/power/supply/charger-manager.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/afe3202c30bdff0635818ab525fe2694309d2692
https://git.kernel.org/stable/c/93b99b63ad5657225faf702670ddfeddf1f0ae29
https://git.kernel.org/stable/c/6f75912cc6ff4c05ff13af351c4eea49b6b3c078
https://git.kernel.org/stable/c/e44ad91e9f75f3e3ccbdb85ffe699471f9675e5b
https://git.kernel.org/stable/c/3999f47e4bbf864e3c7fbfd813fb2f651e6b5714
https://git.kernel.org/stable/c/193e6471e985c2f25d09b3fe96ec52f4eab89bd4
https://git.kernel.org/stable/c/e8631b883338ea4c3b5d8ddfbe16407af9f0b4b9
https://git.kernel.org/stable/c/4373cfa38ead58f980362c841b0d0bdf8c4d956c
reply other threads:[~2026-08-15 6:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026081540-CVE-2026-72182-39e5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.