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+0
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-99246 is a race condition vulnerability in the Linux kernel's TIPC (Topology Information and Cluster) subsystem that occurs when the tipc_node_reset_links trace event executes without proper node locking. This permits a use-after-free condition where bearer teardown operations can free link structures while the trace callback is simultaneously attempting to dump them. The vulnerability affects Linux systems running TIPC networking protocol with active tracing enabled, potentially allowing local attackers to trigger kernel memory corruption, denial of service, or privilege escalation. Any system relying on TIPC for cluster communication is vulnerable during concurrent link reset and trace operations.
While CVE-2026-99246 currently maps to zero MITRE ATT&CK techniques and appears unmapped in Casky's skill library, practitioners using Casky.ai would identify the attack surface through resource management and synchronization analysis. Extended reasoning capabilities would detect this as a classic race condition pattern—specifically a time-of-check-time-of-use (TOCTOU) vulnerability affecting kernel data structures. Security teams would benefit from Casky's ability to correlate this with defensive techniques like T1199 (Trusted Relationships) monitoring for unexpected kernel behavior, and T1014 (Rootkit) detection patterns if exploitation leads to kernel-level persistence. Future skill development should map concurrency vulnerabilities in kernel tracing subsystems to enable automated detection of similar unsynchronized access patterns across Linux components.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-99246. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation