From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89463: power: supply: ucs1002: fix use-after-free on remove
Date: Fri, 11 Sep 2026 21:42:32 +0200 [thread overview]
Message-ID: <2026091101-CVE-2026-89463-d81c@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
power: supply: ucs1002: fix use-after-free on remove
ucs1002 has no remove callback, so unbind runs entirely through devm.
The alert IRQ handler queues the health_poll delayed work, and the work
reschedules itself while the chip reports a bad-health condition. devm
frees the alert IRQ, which only synchronizes the handler; it does not
cancel the delayed work, which can then run after devm frees the driver
data and dereference it.
Register health_poll with devm_delayed_work_autocancel() before the
alert IRQ is requested. devm then frees the IRQ before cancelling the
work, so the handler can no longer queue it and the work is cancelled
before the driver data is freed.
This issue was found by an in-house static analysis tool.
The Linux kernel CVE team has assigned CVE-2026-89463 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.10 with commit 81196e2e57fc5b88f6b8ca98372a3dde047aa49d and fixed in 6.12.109 with commit 4ca2a4678202f15eb790eb7f1d562061709caea7
Issue introduced in 5.10 with commit 81196e2e57fc5b88f6b8ca98372a3dde047aa49d and fixed in 6.18.50 with commit 39b60d615dfa1725c235351fb12bc72e5f8a8d32
Issue introduced in 5.10 with commit 81196e2e57fc5b88f6b8ca98372a3dde047aa49d and fixed in 7.2.4 with commit 35242c93d35f391afdc84cef6236b8ad57f1df24
Issue introduced in 5.10 with commit 81196e2e57fc5b88f6b8ca98372a3dde047aa49d and fixed in 7.3-rc1 with commit 609af0ceeaefdfa42cd01dd060b20f2e41f9a232
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-89463
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/ucs1002_power.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/4ca2a4678202f15eb790eb7f1d562061709caea7
https://git.kernel.org/stable/c/39b60d615dfa1725c235351fb12bc72e5f8a8d32
https://git.kernel.org/stable/c/35242c93d35f391afdc84cef6236b8ad57f1df24
https://git.kernel.org/stable/c/609af0ceeaefdfa42cd01dd060b20f2e41f9a232
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=2026091101-CVE-2026-89463-d81c@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.