From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89475: power: supply: bq24257: fix use-after-free on remove
Date: Fri, 11 Sep 2026 21:42:44 +0200 [thread overview]
Message-ID: <2026091104-CVE-2026-89475-5257@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
power: supply: bq24257: fix use-after-free on remove
The STAT-pin interrupt is devm-managed, so it stays armed until the devm
cleanup that runs after remove() returns. remove() cancels
bq->iilimit_setup_work while the threaded handler can still fire; that
handler reschedules the work and dereferences bq, so the work runs
against freed memory once devm frees bq.
Make the delayed work device-managed with devm_delayed_work_autocancel(),
registered before the interrupt request. The devm cleanup then releases
the interrupt first, so the handler can no longer reschedule the work,
and cancels the work before bq is freed. The explicit
cancel_delayed_work_sync() in remove() is no longer needed and is dropped.
Found by static analysis.
The Linux kernel CVE team has assigned CVE-2026-89475 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.2 with commit 2219a935963e5eeb19e5abfb99475fcc06bbb804 and fixed in 6.12.109 with commit 861ec73ce86e2ca18082cc7be4f140a5bbdf1428
Issue introduced in 4.2 with commit 2219a935963e5eeb19e5abfb99475fcc06bbb804 and fixed in 6.18.50 with commit f495808cdd6d9576965787cf6d9737d0b0e86b73
Issue introduced in 4.2 with commit 2219a935963e5eeb19e5abfb99475fcc06bbb804 and fixed in 7.2.4 with commit 47ccbad210f48721c30d69d65b83dc9fff919ca9
Issue introduced in 4.2 with commit 2219a935963e5eeb19e5abfb99475fcc06bbb804 and fixed in 7.3-rc1 with commit 9d34c9d660c3d0931d2cc749c46c47cf31f96e48
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-89475
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/bq24257_charger.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/861ec73ce86e2ca18082cc7be4f140a5bbdf1428
https://git.kernel.org/stable/c/f495808cdd6d9576965787cf6d9737d0b0e86b73
https://git.kernel.org/stable/c/47ccbad210f48721c30d69d65b83dc9fff919ca9
https://git.kernel.org/stable/c/9d34c9d660c3d0931d2cc749c46c47cf31f96e48
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=2026091104-CVE-2026-89475-5257@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.