From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-46293: clk: microchip: mpfs-ccc: fix out of bounds access during output registration
Date: Mon, 8 Jun 2026 17:46:01 +0200 [thread overview]
Message-ID: <2026060857-CVE-2026-46293-b59c@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
clk: microchip: mpfs-ccc: fix out of bounds access during output registration
UBSAN reported an out of bounds access during registration of the last
two outputs. This out of bounds access occurs because space is only
allocated in the hws array for two PLLs and the four output dividers
that each has, but the defined IDs contain two DLLS and their two
outputs each, which are not supported by the driver. The ID order is
PLLs -> DLLs -> PLL outputs -> DLL outputs. Decrement the PLL output IDs
by two while adding them to the array to avoid the problem.
The Linux kernel CVE team has assigned CVE-2026-46293 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.1 with commit d39fb172760e426e0628f16b785c85e16d17bd5e and fixed in 6.1.175 with commit 9ed9b580a814773482c0a4f1be045636e68cc109
Issue introduced in 6.1 with commit d39fb172760e426e0628f16b785c85e16d17bd5e and fixed in 6.6.140 with commit 47bc7a03449c39805bc2665d3e57c73195d5bcf8
Issue introduced in 6.1 with commit d39fb172760e426e0628f16b785c85e16d17bd5e and fixed in 6.12.88 with commit dbfcb09656cb30439577325c9dea2250203c2e3c
Issue introduced in 6.1 with commit d39fb172760e426e0628f16b785c85e16d17bd5e and fixed in 6.18.30 with commit a0780aeea166a7cf4706c45af4cadbb2a43a1fc9
Issue introduced in 6.1 with commit d39fb172760e426e0628f16b785c85e16d17bd5e and fixed in 7.0.7 with commit f24efd415455b98a1f1cfc6071fe6fde71986706
Issue introduced in 6.1 with commit d39fb172760e426e0628f16b785c85e16d17bd5e and fixed in 7.1-rc1 with commit 2f7ae8ab6aa73daaf080d5332110357c29df9c36
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-46293
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/microchip/clk-mpfs-ccc.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/9ed9b580a814773482c0a4f1be045636e68cc109
https://git.kernel.org/stable/c/47bc7a03449c39805bc2665d3e57c73195d5bcf8
https://git.kernel.org/stable/c/dbfcb09656cb30439577325c9dea2250203c2e3c
https://git.kernel.org/stable/c/a0780aeea166a7cf4706c45af4cadbb2a43a1fc9
https://git.kernel.org/stable/c/f24efd415455b98a1f1cfc6071fe6fde71986706
https://git.kernel.org/stable/c/2f7ae8ab6aa73daaf080d5332110357c29df9c36
reply other threads:[~2026-06-08 15:47 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=2026060857-CVE-2026-46293-b59c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox