data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-46293 in the interactive tracker

CVE-2026-46293

clk: microchip: mpfs-ccc: fix out of bounds access during output registration

EPSS 0.2%

Published 2026-06-08 (4 months ago) by the Linux kernel CNA. Subsystem drivers/clk. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2026-46293 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormwon't fix6.1.190-1Debian has decided against an update for bookworm: Architecture not supported. Moving to a newer release is the way to get the fix.
Debian 13trixiefixed6.12.88-1Update the kernel and reboot. Fixed in 6.12.88-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed7.0.7-1Update the kernel and reboot. Fixed in 7.0.7-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.0.7-1Update the kernel and reboot. Fixed in 7.0.7-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

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.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/clk/microchip/clk-mpfs-ccc.c

What this is
RISC-V MICROCHIP SUPPORTMAINTAINERS section matched on drivers/clk/microchip/clk-mpfs*.c · linux-riscv@lists.infradead.org · Supported

Check it on the machine

grep -w CONFIG_MCHP_CLK_MPFS /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian does not build this code in 1 release. It does build it in 3 releases, so the answer depends on which release the machine runs.

  • bookwormn
  • trixieYnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, armel/rpi, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, s390x/s390x
  • forky, sidYnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt-amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt-arm64, armhf/armmp, armhf/armmp-lpae, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, s390x/s390x
n
not enabled on any flavour - this release does not build the code
Y
built in where it is built at all; some flavours do not build it
Build switch
CONFIG_MCHP_CLK_MPFS

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-06-08 (4 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.17%, higher than 5.5% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
drivers/clk

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
6.16.1.1759ed9b580a814
6.16.6.14047bc7a03449c
6.16.12.88dbfcb09656cb
6.16.18.30a0780aeea166
6.17.0.7f24efd415455
6.17.12f7ae8ab6aa7

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-46293, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.