Invalid memory access via unlocked trace dump
Published Nov 3, 2026 · Updated Nov 3, 2026
Use-after-free in Linux TIPC tracing allows attackers to trigger invalid kernel memory reads during concurrent link teardown. The tipc_node_reset_links trace event calls tipc_node_dump() without the node lock, allowing bearer teardown to free a link before tipc_link_dump() reads it. Reaching the stale read requires active tracing and concurrent link deletion; the published evidence establishes an invalid read, not code execution or a specific service-interruption outcome.
Summary
What happened
Use-after-free in Linux TIPC tracing allows attackers to trigger invalid kernel memory reads during concurrent link teardown. The tipc_node_reset_links trace event calls tipc_node_dump() without the node lock, allowing bearer teardown to free a link before tipc_link_dump() reads it. Reaching the stale read requires active tracing and concurrent link deletion; the published evidence establishes an invalid read, not code execution or a specific service-interruption outcome.
The record
- CVE
- CVE-2026-99246
- Published
- Nov 3, 2026
- Updated
- Nov 3, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 3, 2026CVE publishedPublication date reported by the CVE source.
- Nov 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.0
- Affected versionversion=eb18a510b5cd4daeb9736ad8db57a9fc49db185b <6abd93d01b0f495f29201925a5ee8e6a583c4044
- Affected versionversion=eb18a510b5cd4daeb9736ad8db57a9fc49db185b <6e492cb98ca69cc1145175e23e22e3b84da7f26d
- Affected versionversion=eb18a510b5cd4daeb9736ad8db57a9fc49db185b <7bb6a35bd6d69019539d8782fb590fd2aa8a3236
- Affected versionversion=eb18a510b5cd4daeb9736ad8db57a9fc49db185b <a6101d62ccfa153db8c218ce59362b8e0316fd4f
- Affected versionversion=eb18a510b5cd4daeb9736ad8db57a9fc49db185b <b8b7d28dc2b7472ffd1eff3954c38f1976b21a7b
- Affected versionversion=eb18a510b5cd4daeb9736ad8db57a9fc49db185b <c8b72ca0918e95f708f67c8b3e69b05290f2b6d2
- Affected versionversion=eb18a510b5cd4daeb9736ad8db57a9fc49db185b <dddf197f29ba5e47a476dde82bf542ca2e0d5e5e
- Affected versionversion=eb18a510b5cd4daeb9736ad8db57a9fc49db185b <fa8c78c0e49aa11fae116fd841e41aa8f2d68751
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us