HighCVE-2026-46293

    Linux Kernel: Out-of-Bounds Access (CVE-2026-46293)

    Published Last modified Sources: Ubuntu, BSI, Msrc Update Guide, CVE.org

    What is affected, what to do

    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.

    Update Linux Kernel to version 6.1.175, Linux Kernel to version 6.6.140, Linux Kernel to version 6.12.88.

    Affected
    • Linux Kernel lt 6.1..6.1.175
    • Linux Kernel lt 6.2..6.6.140
    • Linux Kernel lt 6.7..6.12.88
    • Linux Kernel lt 6.13..6.18.30
    • Linux Kernel lt 6.19..7.0.7
    Fixed in
    • Linux Kernel 6.1.175
    • Linux Kernel 6.6.140
    • Linux Kernel 6.12.88
    • Linux Kernel 6.18.30
    • Linux Kernel 7.0.7
    • Linux Kernel 7.1

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.1

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.1

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: Ubuntu, BSI, Msrc Update Guide, CVE.org

    0.1 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 2.3

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    54.21 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.1 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.1
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.1 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    2.3
    Low — this CVE sits in the lower 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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: Ubuntu Security Notices, BSI WID Portal, BSI CSAF, Microsoft Security Update Guide, cvelistv5, NVD (NIST), CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    LinuxLinux
    • 6.7 – < 6.12.88
    • 6.2 – < 6.6.140
    • 6.19 – < 7.0.7
    • —
    • 6.1 – < 6.1.175
    • 6.13 – < 6.18.30
    • 6.12.88
    • 6.6.140
    • 7.0.7
    • 7.1
    • 6.1.175
    • 6.18.30

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxubuntulinux-oracle-7.0noble
    Linuxlinuxlinux_kernel—

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. ReceivedLinux

      Description added or changed

      Show 7 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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.
      Referenceadded
      —
      https://git.kernel.org/stable/c/2f7ae8ab6aa73daaf080d5332110357c29df9c36
      Referenceadded
      —
      https://git.kernel.org/stable/c/47bc7a03449c39805bc2665d3e57c73195d5bcf8
      Referenceadded
      —
      https://git.kernel.org/stable/c/9ed9b580a814773482c0a4f1be045636e68cc109
      Referenceadded
      —
      https://git.kernel.org/stable/c/a0780aeea166a7cf4706c45af4cadbb2a43a1fc9
      Referenceadded
      —
      https://git.kernel.org/stable/c/dbfcb09656cb30439577325c9dea2250203c2e3c
      Referenceadded
      —
      https://git.kernel.org/stable/c/f24efd415455b98a1f1cfc6071fe6fde71986706

      Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    One NVD translation into another language is hidden.

    Linked advisories

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-46293
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-46293"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-46293.svg?lang=en" alt="CVE-2026-46293 – NEOSEC Intel" height="20"></a>