CyberSecBulletin
CVE-2026-46293NVD status: Analyzed

Linux: Out-of-bounds Read

Published Updated By the CyberSecBulletin desk

CVE-2026-46293 is a high-severity out-of-bounds read vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 9ed9b580a814773482c0a4f1be045636e68cc109, 47bc7a03449c39805bc2665d3e57c73195d5bcf8, dbfcb09656cb30439577325c9dea2250203c2e3c as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.13% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 9ed9b580a814773482c0a4f1be045636e68cc109 or 47bc7a03449c39805bc2665d3e57c73195d5bcf8 or dbfcb09656cb30439577325c9dea2250203c2e3c or a0780aeea166a7cf4706c45af4cadbb2a43a1fc9, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.1.175 or 6.6.140 or 6.12.88 or 6.18.30, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxd39fb172760e426e0628f16b785c85e16d17bd5e up to, but not including, 9ed9b580a814773482c0a4f1be045636e68cc109; d39fb172760e426e0628f16b785c85e16d17bd5e up to, but not including, 47bc7a03449c39805bc2665d3e57c73195d5bcf8; d39fb172760e426e0628f16b785c85e16d17bd5e up to, but not including, dbfcb09656cb30439577325c9dea2250203c2e3c; d39fb172760e426e0628f16b785c85e16d17bd5e up to, but not including, a0780aeea166a7cf4706c45af4cadbb2a43a1fc9; d39fb172760e426e0628f16b785c85e16d17bd5e up to, but not including, f24efd415455b98a1f1cfc6071fe6fde71986706; d39fb172760e426e0628f16b785c85e16d17bd5e up to, but not including, 2f7ae8ab6aa73daaf080d5332110357c29df9c36; 6.19ed9b580a814773482c0a4f1be045636e68cc109, 47bc7a03449c39805bc2665d3e57c73195d5bcf8, dbfcb09656cb30439577325c9dea2250203c2e3c, a0780aeea166a7cf4706c45af4cadbb2a43a1fc9, f24efd415455b98a1f1cfc6071fe6fde71986706, 2f7ae8ab6aa73daaf080d5332110357c29df9c36
LinuxLinux Kernel6.1 up to, but not including, 6.1.175; 6.2 up to, but not including, 6.6.140; 6.7 up to, but not including, 6.12.88; 6.13 up to, but not including, 6.18.30; 6.19 up to, but not including, 7.0.76.1.175, 6.6.140, 6.12.88, 6.18.30, 7.0.7

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. Scored by NVD.

Official 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Read

The product reads data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that provides appropriate memory abstractions.

More Out-of-bounds Read vulnerabilities (CWE-125)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Read vulnerabilities

Spotted an error? Tell us.