HighCVE-2026-99246

    Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

    Published Sources: BSI

    Share

    What is affected, what to do

    In the Linux kernel, the following vulnerability has been resolved: tipc: protect node reset trace dump with node lock The tipc_node_reset_links trace event asks tipc_node_dump() to walk the node's link entries. Unlike the other node events that request link data, this event runs without the node lock.

    Update Linux Kernel to version 5.10.273, Linux Kernel to version 5.15.224, Linux Kernel to version 6.1.191.

    Affected
    • Linux Kernel lt 5.0..5.10.273
    • Linux Kernel lt 5.11..5.15.224
    • Linux Kernel lt 5.16..6.1.191
    • Linux Kernel lt 6.2..6.6.161
    • Linux Kernel lt 6.7..6.12.115
    • Linux Kernel lt 6.13..6.18.59
    • Linux Kernel lt 6.19..7.2.13
    Fixed in
    • Linux Kernel 5.10.273
    • Linux Kernel 5.15.224
    • Linux Kernel 6.1.191
    • Linux Kernel 6.6.161
    • Linux Kernel 6.12.115
    • Linux Kernel 6.18.59
    • Linux Kernel 7.2.13
    • Linux Kernel 7.3

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

    Metrics

    8.1

    Priority

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

    Source: Vendor (CNA), CVSS v3

    8.1

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: BSI

    0.4 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 38.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
    69.37 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.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
    8.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.4 %
    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
    38.7
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    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: tipc: protect node reset trace dump with node lock The tipc_node_reset_links trace event asks tipc_node_dump() to walk the node's link entries. Unlike the other node events that request link data, this event runs without the node lock. This permits bearer teardown to free a link while the trace callback is dumping it: CPU 0 CPU 1 trace_tipc_node_reset_links() tipc_node_dump() l = n->links[0].link tipc_node_write_lock() kfree(l) n->links[0].link = NULL tipc_node_write_unlock() tipc_link_dump(l) tipc_link_dump() then dereferences the stale pointer. KASAN reported: BUG: KASAN: slab-use-after-free in tipc_link_dump Read of size 4 by task poc/115 Call Trace: tipc_link_dump+0x10cb/0x16b0 tipc_node_dump+0x4bb/0x740 trace_event_raw_event_tipc_node_class+0x258/0x360 tipc_node_reset_links+0x14d/0x1a0 tipc_rcv+0x13f5/0x3030 tipc_udp_recv+0x4e3/0x670 Allocated by task 0: tipc_link_create+0x1e1/0x1020 tipc_node_check_dest+0x7d2/0x11a0 tipc_disc_rcv+0xdbf/0x1430 Freed by task 89: kfree+0x131/0x3c0 tipc_node_link_down+0x267/0x4b0 tipc_node_delete_links+0xec/0x160 bearer_disable+0x107/0x260 Take the node write lock around the trace event. This serializes the dump against tipc_node_link_down(delete=true), which frees the link under the same write lock.

    Source: BSI WID Portal

    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
    • 2.6.24 – < 6.1.191
    • 2.6.27 – < 6.1.191
    • 2.6.30 – < 5.10.273
    • 3.13 – < 5.10.273
    • 3.18 – < 5.10.273
    • 4.12 – < 5.10.273
    • 4.14.177 – < 4.15
    • 4.17 – < 5.10.273
    • 4.17 – < 6.1.191
    • 4.19.118 – < 4.20
    • 4.20 – < 6.1.191
    • 4.7 – < 5.10.273
    • 5.0 – < 5.10.273
    • 5.10.221 – < 5.11
    • 5.10.265 – < 5.10.273
    • 5.11 – < 5.15.224
    • 5.12 – < 6.1.191
    • 5.13 – < 5.15.224
    • 5.15.11 – < 5.15.224
    • 5.15.162 – < 5.16
    • 5.15.216 – < 5.15.224
    • 5.15.82 – < 5.16
    • 5.16 – < 6.1.191
    • 5.19 – < 6.1.191
    • 5.3 – < 5.10.273
    • 5.4.35 – < 5.5
    • 5.5 – < 6.1.191
    • 5.6 – < 6.1.191
    • 5.6.7 – < 5.7
    • 5.7 – < 5.10.273
    • 6.0.11 – < 6.1
    • 6.1 – < 6.1.191
    • 6.10 – < 6.12.115
    • 6.1.183 – < 6.1.191
    • 6.12 – < 6.12.115
    • 6.12.113 – < 6.12.115
    • 6.12.41 – < 6.12.115
    • 6.12.44 – < 6.12.115
    • 6.12.97 – < 6.12.115
    • 6.13 – < 6.18.59
    • 6.13 – < 6.18.60
    • 6.15 – < 6.18.60
    • 6.15.11 – < 6.16
    • 6.15.3 – < 6.16
    • 6.16 – < 6.18.59
    • 6.16 – < 6.18.60
    • 6.16.2 – < 6.17
    • 6.17 – < 6.18.60
    • 6.1.191
    • 6.1.191
    • 5.10.273
    • 5.10.273
    • 5.10.273
    • 5.10.273
    • 4.15
    • 5.10.273
    • 6.1.191
    • 4.20
    • 6.1.191
    • 5.10.273
    • 5.10.273
    • 5.11
    • 5.10.273
    • 5.15.224
    • 6.1.191
    • 5.15.224
    • 5.15.224
    • 5.16
    • 5.15.224
    • 5.16
    • 6.1.191
    • 6.1.191
    • 5.10.273
    • 5.5
    • 6.1.191
    • 6.1.191
    • 5.7
    • 5.10.273
    • 6.1
    • 6.1.191
    • 6.12.115
    • 6.1.191
    • 6.12.115
    • 6.12.115
    • 6.12.115
    • 6.12.115
    • 6.12.115
    • 6.18.59
    • 6.18.60
    • 6.18.60
    • 6.16
    • 6.16
    • 6.18.59
    • 6.18.60
    • 6.17
    • 6.18.60

    Vendors and products

    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 modifiedLinux

      CVSS V3.1: AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      CVSSadded
      —
      AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

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

    2. ReceivedLinux

      Description added or changed

      Show 10 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      In the Linux kernel, the following vulnerability has been resolved: tipc: protect node reset trace dump with node lock The tipc_node_reset_links trace event asks tipc_node_dump() to walk the node's link entries. Unlike the other node events that request link data, this event runs without the node lock. This permits bearer teardown to free a link while the trace callback is dumping it: CPU 0 CPU 1 trace_tipc_node_reset_links() tipc_node_dump() l = n->links[0].link tipc_node_write_lock() kfree(l) n->links[0].link = NULL tipc_node_write_unlock() tipc_link_dump(l) tipc_link_dump() then dereferences the stale pointer. KASAN reported: BUG: KASAN: slab-use-after-free in tipc_link_dump Read of size 4 by task poc/115 Call Trace: tipc_link_dump+0x10cb/0x16b0 tipc_node_dump+0x4bb/0x740 trace_event_raw_event_tipc_node_class+0x258/0x360 tipc_node_reset_links+0x14d/0x1a0 tipc_rcv+0x13f5/0x3030 tipc_udp_recv+0x4e3/0x670 Allocated by task 0: tipc_link_create+0x1e1/0x1020 tipc_node_check_dest+0x7d2/0x11a0 tipc_disc_rcv+0xdbf/0x1430 Freed by task 89: kfree+0x131/0x3c0 tipc_node_link_down+0x267/0x4b0 tipc_node_delete_links+0xec/0x160 bearer_disable+0x107/0x260 Take the node write lock around the trace event. This serializes the dump against tipc_node_link_down(delete=true), which frees the link under the same write lock.
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/99xxx/CVE-2026-99246.json">CVE-2026-99246</a>
      Referenceadded
      —
      https://git.kernel.org/stable/c/6abd93d01b0f495f29201925a5ee8e6a583c4044
      Referenceadded
      —
      https://git.kernel.org/stable/c/6e492cb98ca69cc1145175e23e22e3b84da7f26d
      Referenceadded
      —
      https://git.kernel.org/stable/c/7bb6a35bd6d69019539d8782fb590fd2aa8a3236
      Referenceadded
      —
      https://git.kernel.org/stable/c/a6101d62ccfa153db8c218ce59362b8e0316fd4f
      Referenceadded
      —
      https://git.kernel.org/stable/c/b8b7d28dc2b7472ffd1eff3954c38f1976b21a7b
      Referenceadded
      —
      https://git.kernel.org/stable/c/c8b72ca0918e95f708f67c8b3e69b05290f2b6d2
      Referenceadded
      —
      https://git.kernel.org/stable/c/dddf197f29ba5e47a476dde82bf542ca2e0d5e5e
      Referenceadded
      —
      https://git.kernel.org/stable/c/fa8c78c0e49aa11fae116fd841e41aa8f2d68751

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

    Linked CVEs

    Linked CVEs
    HighCVE-2026-99269Linux Kernel: security vulnerability7.8—
    LowCVE-2026-99268Linux Kernel: security vulnerability3.3—
    Not ratedCVE-2026-99267Linux Kernel: security vulnerability——
    Not ratedCVE-2026-99266Linux Kernel: security vulnerability——
    Not ratedCVE-2026-99265Linux Kernel: security vulnerability——
    HighCVE-2026-99264Linux Kernel: security vulnerability7.8—
    LowCVE-2026-99263Linux Kernel: security vulnerability2.5—
    MediumCVE-2026-99262Linux Kernel: security vulnerability4.7—
    LowCVE-2026-99261Linux Kernel: security vulnerability3.3—
    LowCVE-2026-99260Linux Kernel: security vulnerability3.3—
    Not ratedCVE-2026-99259Linux Kernel: security vulnerability——
    Not ratedCVE-2026-99258Linux Kernel: security vulnerability——
    Not ratedCVE-2026-99257Linux Kernel: security vulnerability——
    LowCVE-2026-99256Linux Kernel: security vulnerability2.3—
    MediumCVE-2026-99255Linux Kernel: security vulnerability4.7—
    MediumCVE-2026-99254Linux Kernel: security vulnerability5.5—
    Not ratedCVE-2026-99253Linux Kernel: security vulnerability——
    Not ratedCVE-2026-99252Linux Kernel: security vulnerability——
    MediumCVE-2026-99251Linux Kernel: Infinite Loop4.1—
    Not ratedCVE-2026-99250Linux Kernel: security vulnerability——
    LowCVE-2026-99249Linux Kernel: security vulnerability2.5—
    Not ratedCVE-2026-99248Linux Kernel: security vulnerability——
    MediumCVE-2026-99247Linux Kernel: NULL Pointer Dereference4.1—
    HighCVE-2026-99246Linux Kernel: Use-After-Free8.1—
    Show 29 more CVEs
    Linked CVEs
    MediumCVE-2026-99245Linux Kernel: security vulnerability4.7—
    Not ratedCVE-2026-99244Linux Kernel: security vulnerability——
    MediumCVE-2026-99243Linux Kernel: security vulnerability4.7—
    Not ratedCVE-2026-99242Linux Kernel: Information Disclosure——
    Not ratedCVE-2026-99241Linux Kernel: security vulnerability——
    Not ratedCVE-2026-99240Linux Kernel: Divide By Zero——
    HighCVE-2026-99239Linux Kernel: security vulnerability7.8—
    HighCVE-2026-99238Linux Kernel: security vulnerability7.8—
    HighCVE-2026-99237Linux Kernel: security vulnerability7.8—
    MediumCVE-2026-99236Linux Kernel: Out-of-Bounds Access5.5—
    MediumCVE-2026-99235Linux Kernel: Use-After-Free4.4—
    LowCVE-2026-99234Linux Kernel: security vulnerability3.4—
    MediumCVE-2026-99233Linux Kernel: security vulnerability4.4—
    Not ratedCVE-2026-99232Linux Kernel: security vulnerability——
    HighCVE-2026-99231Linux Kernel: Use-After-Free7.8—
    Not ratedCVE-2026-99230Linux Kernel: security vulnerability——
    MediumCVE-2026-99229Linux Kernel: security vulnerability5.5—
    Not ratedCVE-2026-99228Linux Kernel: security vulnerability——
    HighCVE-2026-99227Linux Kernel: security vulnerability7.8—
    MediumCVE-2026-99226Linux Kernel: Use-After-Free4.7—
    MediumCVE-2026-99225Linux Kernel: NULL Pointer Dereference4.7—
    MediumCVE-2026-99224Linux Kernel: security vulnerability5.3—
    LowCVE-2026-99223Linux Kernel: security vulnerability3.3—
    MediumCVE-2026-99222Linux Kernel: security vulnerability4.7—
    LowCVE-2026-99221Linux Kernel: security vulnerability2.5—
    MediumCVE-2026-99220Linux Kernel: NULL Pointer Dereference5.5—
    MediumCVE-2026-99219Linux Kernel: security vulnerability4.1—
    MediumCVE-2026-99218Linux Kernel: security vulnerability4.7—
    Not ratedCVE-2026-99217Linux Kernel: Deadlock——
    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-99246
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-99246"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-99246.svg?lang=en" alt="CVE-2026-99246 – NEOSEC Intel" height="20"></a>