HighCVE-2026-46307

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

    Published Last modified Sources: SUSE, Debian LTS, Ubuntu, Siemens ProductCERT, BSI, CVE.org, Msrc Update Guide

    What is affected, what to do

    In the Linux kernel, the following vulnerability has been resolved: wifi: ath5k: do not access array OOB Vincent reports: > The ath5k driver seems to do an array-index-out-of-bounds access as > shown by the UBSAN kernel message: > UBSAN: array-index-out-of-bounds in drivers/net/wireless/ath/ath5k/base.c:1741:20 > index 4 is out of range for type 'ieee80211_tx_rate [4]' > ... > Call Trace: > <TASK> > dump_stack_lvl+0x5d/0x80 > ubsan_epilogue+0x5/0x2b > __ubsan_handle_out_of_bounds.cold+0x46/0x4b > ath5k_tasklet_tx+0x4e0/0x560 [ath5k] > tasklet_action_common+0xb5/0x1c0 It is real. 'ts->ts_final_idx' can be 3 on 5212, so: info->status.rates[ts->ts_final_idx + 1].idx = -1; with the array defined as: struct ieee80211_tx_rate rates[IEEE80211_TX_MAX_RATES]; while the size is: #define IEEE80211_TX_MAX_RATES 4 is indeed bogus. Set this 'idx = -1' sentinel only if the array index is less than the array size.

    Update Linux Kernel to version 5.10.258, Linux Kernel to version 5.15.209, Linux Kernel to version 6.1.175.

    Affected
    • Linux Kernel lt 3.0..5.10.258
    • Linux Kernel lt 5.11..5.15.209
    • Linux Kernel lt 5.16..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 5.10.258
    • Linux Kernel 5.15.209
    • 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

    8.3

    Priority

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

    Source: Vendor (CNA), CVSS v3

    8.3

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: SUSE, Debian LTS, Ubuntu, Siemens ProductCERT, BSI, CVE.org, Msrc Update Guide

    0.2 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 14.7

    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
    61.79 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
    8.3 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
    8.3
    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.2 %
    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
    14.7
    Elevated — this CVE ranks above at least 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: wifi: ath5k: do not access array OOB Vincent reports: > The ath5k driver seems to do an array-index-out-of-bounds access as > shown by the UBSAN kernel message: > UBSAN: array-index-out-of-bounds in drivers/net/wireless/ath/ath5k/base.c:1741:20 > index 4 is out of range for type 'ieee80211_tx_rate [4]' > ... > Call Trace: > <TASK> > dump_stack_lvl+0x5d/0x80 > ubsan_epilogue+0x5/0x2b > __ubsan_handle_out_of_bounds.cold+0x46/0x4b > ath5k_tasklet_tx+0x4e0/0x560 [ath5k] > tasklet_action_common+0xb5/0x1c0 It is real. 'ts->ts_final_idx' can be 3 on 5212, so: info->status.rates[ts->ts_final_idx + 1].idx = -1; with the array defined as: struct ieee80211_tx_rate rates[IEEE80211_TX_MAX_RATES]; while the size is: #define IEEE80211_TX_MAX_RATES 4 is indeed bogus. Set this 'idx = -1' sentinel only if the array index is less than the array size. As mac80211 will not look at rates beyond the size (IEEE80211_TX_MAX_RATES). Note: The effect of the OOB write is negligible. It just overwrites the next member of info->status, i.e. ack_signal.

    Source: suse_csaf, Debian LTS Advisories, Ubuntu Security Notices, siemens_advisory, BSI WID Portal, BSI CSAF, cvelistv5, NVD (NIST), Microsoft Security Update Guide, 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
    • 5.16 – < 6.1.175
    • 6.7 – < 6.12.88
    • 6.2 – < 6.6.140
    • 6.19 – < 7.0.7
    • 5.11 – < 5.15.209
    • —
    • 3.0 – < 5.10.258
    • 6.13 – < 6.18.30
    • 6.1.175
    • 6.12.88
    • 6.6.140
    • 7.0.7
    • 5.15.209
    • 7.1
    • 5.10.258
    • 6.18.30
    SiemensSIMATIC S7
    • 1500 TM MFP V1.1.1 GNU/Linux subsystem
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Linuxdebianlinuxbookworm
    Linuxdebianlinuxbullseye
    Linuxdebianlinux-6.1bullseye
    Linuxubuntulinux-oracle-7.0noble
    Linuxlinuxlinux_kernel7.1
    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. Record modifiedSiemens ADP

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/46xxx/CVE-2026-46307.json">CVE-2026-46307</a>
      Referenceadded
      —
      https://cert-portal.siemens.com/productcert/html/ssa-784472.html

      Source identifier: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e

    2. Record modifiedLinux

      Show 24 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://git.kernel.org/stable/c/568173ad9bd0b46cc6cd937dea8791e9b5eefa57
      Referenceadded
      —
      https://git.kernel.org/stable/c/744c19e266b0d2628c5951439195dcef27eadacf
      Referenceadded
      —
      https://git.kernel.org/stable/c/83226c71af53fb9b3cad40cb9a9a79f36d68c020
      Referenceadded
      —
      https://git.kernel.org/stable/c/9dd6aae4bc7bfa11088d928670a3315eae542769
      Referenceadded
      —
      https://git.kernel.org/stable/c/d6869537013b1f21b292342752d97868b79b5934
      Referenceadded
      —
      https://git.kernel.org/stable/c/d748603f12baff112caa3ab7d39f50100f010dbd
      Referenceadded
      —
      https://git.kernel.org/stable/c/e9f1081bc775146156def0dbc821b92f35d56afb
      Referenceadded
      —
      https://git.kernel.org/stable/c/ecb1c163166759dec004c1fdb9709b8a5992fc8e
      Referenceremoved
      https://git.kernel.org/stable/c/568173ad9bd0b46cc6cd937dea8791e9b5eefa57
      —
      Referenceremoved
      https://git.kernel.org/stable/c/744c19e266b0d2628c5951439195dcef27eadacf
      —
      Referenceremoved
      https://git.kernel.org/stable/c/83226c71af53fb9b3cad40cb9a9a79f36d68c020
      —
      Referenceremoved
      https://git.kernel.org/stable/c/9dd6aae4bc7bfa11088d928670a3315eae542769
      —
      Referenceremoved
      https://git.kernel.org/stable/c/d6869537013b1f21b292342752d97868b79b5934
      —
      Referenceremoved
      https://git.kernel.org/stable/c/d748603f12baff112caa3ab7d39f50100f010dbd
      —
      Referenceremoved
      https://git.kernel.org/stable/c/e9f1081bc775146156def0dbc821b92f35d56afb
      —
      Referenceremoved
      https://git.kernel.org/stable/c/ecb1c163166759dec004c1fdb9709b8a5992fc8e
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/568173ad9bd0b46cc6cd937dea8791e9b5eefa57 Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/744c19e266b0d2628c5951439195dcef27eadacf Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/83226c71af53fb9b3cad40cb9a9a79f36d68c020 Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/9dd6aae4bc7bfa11088d928670a3315eae542769 Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/d6869537013b1f21b292342752d97868b79b5934 Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/d748603f12baff112caa3ab7d39f50100f010dbd Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/e9f1081bc775146156def0dbc821b92f35d56afb Types: Patch
      —
      Reference typeremoved
      https://git.kernel.org/stable/c/ecb1c163166759dec004c1fdb9709b8a5992fc8e Types: Patch
      —

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

    3. ReceivedLinux

      Description added or changed

      Show 9 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      In the Linux kernel, the following vulnerability has been resolved: wifi: ath5k: do not access array OOB Vincent reports: > The ath5k driver seems to do an array-index-out-of-bounds access as > shown by the UBSAN kernel message: > UBSAN: array-index-out-of-bounds in drivers/net/wireless/ath/ath5k/base.c:1741:20 > index 4 is out of range for type 'ieee80211_tx_rate [4]' > ... > Call Trace: > <TASK> > dump_stack_lvl+0x5d/0x80 > ubsan_epilogue+0x5/0x2b > __ubsan_handle_out_of_bounds.cold+0x46/0x4b > ath5k_tasklet_tx+0x4e0/0x560 [ath5k] > tasklet_action_common+0xb5/0x1c0 It is real. 'ts->ts_final_idx' can be 3 on 5212, so: info->status.rates[ts->ts_final_idx + 1].idx = -1; with the array defined as: struct ieee80211_tx_rate rates[IEEE80211_TX_MAX_RATES]; while the size is: #define IEEE80211_TX_MAX_RATES 4 is indeed bogus. Set this 'idx = -1' sentinel only if the array index is less than the array size. As mac80211 will not look at rates beyond the size (IEEE80211_TX_MAX_RATES). Note: The effect of the OOB write is negligible. It just overwrites the next member of info->status, i.e. ack_signal.
      Referenceadded
      —
      https://git.kernel.org/stable/c/568173ad9bd0b46cc6cd937dea8791e9b5eefa57
      Referenceadded
      —
      https://git.kernel.org/stable/c/744c19e266b0d2628c5951439195dcef27eadacf
      Referenceadded
      —
      https://git.kernel.org/stable/c/83226c71af53fb9b3cad40cb9a9a79f36d68c020
      Referenceadded
      —
      https://git.kernel.org/stable/c/9dd6aae4bc7bfa11088d928670a3315eae542769
      Referenceadded
      —
      https://git.kernel.org/stable/c/d6869537013b1f21b292342752d97868b79b5934
      Referenceadded
      —
      https://git.kernel.org/stable/c/d748603f12baff112caa3ab7d39f50100f010dbd
      Referenceadded
      —
      https://git.kernel.org/stable/c/e9f1081bc775146156def0dbc821b92f35d56afb
      Referenceadded
      —
      https://git.kernel.org/stable/c/ecb1c163166759dec004c1fdb9709b8a5992fc8e

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

    One NVD translation into another language is hidden.

    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-46307
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-46307"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-46307.svg?lang=en" alt="CVE-2026-46307 – NEOSEC Intel" height="20"></a>