From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-90147: clk: devres: fix cleanup in devm_clk_get_optional_enabled_with_rate()
Date: Thu, 17 Sep 2026 17:09:37 +0100 [thread overview]
Message-ID: <2026091722-CVE-2026-90147-fa43@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
clk: devres: fix cleanup in devm_clk_get_optional_enabled_with_rate()
devm_clk_get_optional_enabled_with_rate() registers its cleanup action
before setting the clock rate. If setting the rate fails, it attempts to
disable and unprepare a clock that was never enabled. This issue was
spotted while reviewing "rust: clk: add devres-managed clks" [1].
Register the cleanup action only after successfully preparing and enabling
the clock.
[1]: https://lore.kernel.org/rust-for-linux/20260706-clk-type-state-v5-3-67c5f326a16c@collabora.com
The Linux kernel CVE team has assigned CVE-2026-90147 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12 with commit 9934a1bd45b2b03f6d1204a6ae2780d3b009799f and fixed in 6.12.110 with commit 9a365f41fe0f227ef5a269e240233bd0bffc66c9
Issue introduced in 6.12 with commit 9934a1bd45b2b03f6d1204a6ae2780d3b009799f and fixed in 6.18.52 with commit 9d4843f1051259854f724e9cdc5b9eac56327037
Issue introduced in 6.12 with commit 9934a1bd45b2b03f6d1204a6ae2780d3b009799f and fixed in 7.2.6 with commit 647157fecb42b72d930e7b7d0bfbc5f2db9a858a
Issue introduced in 6.12 with commit 9934a1bd45b2b03f6d1204a6ae2780d3b009799f and fixed in 7.3-rc1 with commit 0d4d262c1664365e17e0a5ba2ab79f4db484b44e
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-90147
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/clk/clk-devres.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/9a365f41fe0f227ef5a269e240233bd0bffc66c9
https://git.kernel.org/stable/c/9d4843f1051259854f724e9cdc5b9eac56327037
https://git.kernel.org/stable/c/647157fecb42b72d930e7b7d0bfbc5f2db9a858a
https://git.kernel.org/stable/c/0d4d262c1664365e17e0a5ba2ab79f4db484b44e
reply other threads:[~2026-09-17 16:17 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=2026091722-CVE-2026-90147-fa43@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.