CVE-2026-46293
HighIn 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.
CVSS 3.1 score
7.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Weakness type
CWE-125CVE-2026-46293 is a Out-of-bounds Read vulnerability
What is Out-of-bounds Read?
The product reads data past the end or before the beginning of the intended buffer. Learn more on MITRE CWE
Affected versions
Linux kernel versions
6.1
and later are affected. Fixed in
6.1.175,
6.6.140,
6.12.88,
6.18.30,
7.0.7,
7.1
and their respective stable series.
References
6 total-
Patch
-
Patch
-
Patch
-
Patch
-
Patch
Frequently asked questions
-
What is CVE-2026-46293?
CVE-2026-46293 is a High severity Linux kernel vulnerability with a CVSS score of 7.1 out of 10 , classified as an Out-of-bounds Read flaw (CWE-125) . It affects Linux kernel versions from 6.1 onward and has been patched in 6.1.175, 6.6.140, 6.12.88 and others. CVE-2026-46293 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2026-46293?
CVE-2026-46293 has a CVSS score of 7.1 out of 10, rated High severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. -
Is there a patch available for CVE-2026-46293?
Yes. CVE-2026-46293 has been patched. Fixed versions include 6.1.175, 6.6.140, 6.12.88 and others. If you are running Linux kernel 6.1 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-46293 actively exploited?
No. CVE-2026-46293 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.