From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89467: power: supply: qcom_battmgr: fix use-after-free
Date: Fri, 11 Sep 2026 21:42:36 +0200 [thread overview]
Message-ID: <2026091102-CVE-2026-89467-6f38@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
power: supply: qcom_battmgr: fix use-after-free
qcom_battmgr_pdr_notify() queues enable_work when the PMIC GLINK service
comes up, and the worker recovers battmgr through container_of() to issue
firmware requests. The PMIC GLINK client stays on the client list until
its devres release action runs, so a PDR notification can keep queueing
the work, and a pending or running worker can access battmgr after devres
frees it.
Make enable_work device-managed with devm_work_autocancel(), registered
before the PMIC GLINK client is allocated. The devres cleanup then
releases the client first, so no further notification can queue the work,
and cancels the work before battmgr is freed.
This issue was found by an in-house static analysis tool.
The Linux kernel CVE team has assigned CVE-2026-89467 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.3 with commit 29e8142b5623b5949587bcc4f591c4e6595c4aca and fixed in 6.18.50 with commit 06618447029c6dddaa02f6e9528efe5dd49fc329
Issue introduced in 6.3 with commit 29e8142b5623b5949587bcc4f591c4e6595c4aca and fixed in 7.2.4 with commit 49fbcd3da2958159370d25dafbf736e654a4d59b
Issue introduced in 6.3 with commit 29e8142b5623b5949587bcc4f591c4e6595c4aca and fixed in 7.3-rc1 with commit 4e40befedfc8ed86f44e1f81df92d13c149c9f8d
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-89467
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/qcom_battmgr.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/06618447029c6dddaa02f6e9528efe5dd49fc329
https://git.kernel.org/stable/c/49fbcd3da2958159370d25dafbf736e654a4d59b
https://git.kernel.org/stable/c/4e40befedfc8ed86f44e1f81df92d13c149c9f8d
reply other threads:[~2026-09-11 19:51 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=2026091102-CVE-2026-89467-6f38@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.