Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2026-99246

tipc: protect node reset trace dump with node lock

Products / packages Linux

Published

Share

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 06/11/2026, 21:10:31 UTC
Linux · CVSS:3.1 · 8.1
Assessment vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Severity

high8.1

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Fix status not established

No structured fix or guidance is available here. Check the latest publisher advisory.

What this means

The Linux kernel's tipc_node_reset_links trace event may dereference a stale pointer, potentially causing a slab-use-after-free error, due to a lack of node lock protection. This issue affects Linux kernel versions starting from 5.0. The vulnerability requires access to the system and may be triggered by a race condition between the trace event and bearer teardown.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

Linux · Linux

Linux

8 ranges
Linux version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

eb18a510b5cd4daeb9736ad8db57a9fc49db185b → before c8b72ca0918e95f708f67c8b3e69b05290f2b6d2

git versions

eb18a510b5cd4daeb9736ad8db57a9fc49db185b → before 6e492cb98ca69cc1145175e23e22e3b84da7f26d

git versions

eb18a510b5cd4daeb9736ad8db57a9fc49db185b → before 7bb6a35bd6d69019539d8782fb590fd2aa8a3236

git versions

eb18a510b5cd4daeb9736ad8db57a9fc49db185b → before 6abd93d01b0f495f29201925a5ee8e6a583c4044

git versions

eb18a510b5cd4daeb9736ad8db57a9fc49db185b → before a6101d62ccfa153db8c218ce59362b8e0316fd4f

git versions

eb18a510b5cd4daeb9736ad8db57a9fc49db185b → before b8b7d28dc2b7472ffd1eff3954c38f1976b21a7b

git versions

eb18a510b5cd4daeb9736ad8db57a9fc49db185b → before fa8c78c0e49aa11fae116fd841e41aa8f2d68751

git versions

eb18a510b5cd4daeb9736ad8db57a9fc49db185b → before dddf197f29ba5e47a476dde82bf542ca2e0d5e5e

git versions

unaffected

unknown

Other versions: unaffected

Linux · Linux

Linux

10 ranges
Linux version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

5.0

unaffected

0 → before 5.0

semver versions

5.10.273 → through 5.10.*

semver versions

5.15.224 → through 5.15.*

semver versions

6.1.191 → through 6.1.*

semver versions

6.6.161 → through 6.6.*

semver versions

6.12.115 → through 6.12.*

semver versions

6.18.59 → through 6.18.*

semver versions

7.2.13 → through 7.2.*

semver versions

7.3 → through *

original_commit_for_fix versions

unknown

Other versions: affected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher 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.

References

8 sources
git.kernel.org/stable/c/c8b72ca0918e95f708f67c8b3e69b05290f2b6d2
Source referenceLinux
git.kernel.org/stable/c/6e492cb98ca69cc1145175e23e22e3b84da7f26d
Source referenceLinux
git.kernel.org/stable/c/7bb6a35bd6d69019539d8782fb590fd2aa8a3236
Source referenceLinux
git.kernel.org/stable/c/6abd93d01b0f495f29201925a5ee8e6a583c4044
Source referenceLinux
git.kernel.org/stable/c/a6101d62ccfa153db8c218ce59362b8e0316fd4f
Source referenceLinux
git.kernel.org/stable/c/b8b7d28dc2b7472ffd1eff3954c38f1976b21a7b
Source referenceLinux
View 2 more references
git.kernel.org/stable/c/fa8c78c0e49aa11fae116fd841e41aa8f2d68751
Source referenceLinux
git.kernel.org/stable/c/dddf197f29ba5e47a476dde82bf542ca2e0d5e5e
Source referenceLinux

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification · not supplied
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-99246

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

Linux · platform conditions

Any condition may hold

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 5.0

Before: 5.10.273

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 5.0

Before: 5.15.224

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 5.0

Before: 6.1.191

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 5.0

Before: 6.6.161

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 5.0

Before: 6.12.115

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 5.0

Before: 6.18.59

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 5.0

Before: 7.2.13

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 5.0

Before: 7.3

Original applicability statements
[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "5.0",
            "versionEndExcluding": "5.10.273"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "5.0",
            "versionEndExcluding": "5.15.224"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "5.0",
            "versionEndExcluding": "6.1.191"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "5.0",
            "versionEndExcluding": "6.6.161"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "5.0",
            "versionEndExcluding": "6.12.115"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "5.0",
            "versionEndExcluding": "6.18.59"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "5.0",
            "versionEndExcluding": "7.2.13"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "5.0",
            "versionEndExcluding": "7.3"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 1
Linux

Assigning organization

2026-11-03

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
  1. CVE · CVE-2026-99246

    Observed 2026-11-03T19:51:02.578Z · upstream updated 2026-11-03T19:14:37.365Z

    Severity assessment changed

    before

    []

    after

    [
  {
    "source": "Linux",
    "vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
    "score": 8.1
  }
]

Large field values are marked as truncated previews. Original source snapshots remain retained.

Showing up to 50 most recent observed changes.