Skip to main content
No exploitation reportedAwaiting NVD analysis

CVE-2026-99246

tipc: protect node reset trace dump with node lock

No exploitation reported by the sources we read.

  • Published2026-11-03

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-11-0311:18CVE publishedCNA

Observed activity

isMalicious corpus · updated 2026-11-03 15:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-99246?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-99246?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

Products declared by the CNA

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ eb18a510b5cd4daeb9736ad8db57a9fc49db185b, < c8b72ca0918e95f708f67c8b3e69b05290f2b6d2fixed in c8b72ca0918e95f708f67c8b3e69b05290f2b6d2git
    • ≥ eb18a510b5cd4daeb9736ad8db57a9fc49db185b, < 6e492cb98ca69cc1145175e23e22e3b84da7f26dfixed in 6e492cb98ca69cc1145175e23e22e3b84da7f26dgit
    • ≥ eb18a510b5cd4daeb9736ad8db57a9fc49db185b, < 7bb6a35bd6d69019539d8782fb590fd2aa8a3236fixed in 7bb6a35bd6d69019539d8782fb590fd2aa8a3236git
    • ≥ eb18a510b5cd4daeb9736ad8db57a9fc49db185b, < 6abd93d01b0f495f29201925a5ee8e6a583c4044fixed in 6abd93d01b0f495f29201925a5ee8e6a583c4044git
    • ≥ eb18a510b5cd4daeb9736ad8db57a9fc49db185b, < a6101d62ccfa153db8c218ce59362b8e0316fd4ffixed in a6101d62ccfa153db8c218ce59362b8e0316fd4fgit
    • ≥ eb18a510b5cd4daeb9736ad8db57a9fc49db185b, < b8b7d28dc2b7472ffd1eff3954c38f1976b21a7bfixed in b8b7d28dc2b7472ffd1eff3954c38f1976b21a7bgit
    • ≥ eb18a510b5cd4daeb9736ad8db57a9fc49db185b, < fa8c78c0e49aa11fae116fd841e41aa8f2d68751fixed in fa8c78c0e49aa11fae116fd841e41aa8f2d68751git
    • ≥ eb18a510b5cd4daeb9736ad8db57a9fc49db185b, < dddf197f29ba5e47a476dde82bf542ca2e0d5e5efixed in dddf197f29ba5e47a476dde82bf542ca2e0d5e5egit
  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • = 5.0no fix stated

    Not affected < 5.0 · ≥ 5.10.273, ≤ 5.10.* · ≥ 5.15.224, ≤ 5.15.* · ≥ 6.1.191, ≤ 6.1.* · ≥ 6.6.161, ≤ 6.6.* · ≥ 6.12.115, ≤ 6.12.* · ≥ 6.18.59, ≤ 6.18.*

    2 more version lines in the CVE record.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-03

Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-99246 yet.

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2026-11-03
Last Modified
2026-11-03
NVD status
Received
GitHub Advisory
GHSA-qwfh-hpch-ph73

Frequently asked questions

What is CVE-2026-99246?

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.

Is CVE-2026-99246 actively exploited?

Active exploitation of CVE-2026-99246 has not been confirmed.

What is the CVSS score for CVE-2026-99246?

CVE-2026-99246 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record