CVE-2026-99246: Linux kernel · tipc: protect node reset trace dump with node lock
Source GCVE Database
Not known to be exploited · fixed in fa8c78c0e49aa11fae116fd841e41aa8f2d68751 : patch Linux kernel soon.
Data as of 3 Nov 2026, 13:28 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in fa8c78c0e49aa11fae116fd841e41aa8f2d68751, dddf197f29ba5e47a476dde82bf542ca2e0d5e5e, c8b72ca0918e95f708f67c8b3e69b05290f2b6d2 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available that adds the node write lock around the trace event to prevent concurrent access to freed links. Users should apply the official Linux kernel patch that addresses this issue to ensure memory safety in the TIPC subsystem.
Description
A use-after-free vulnerability in the Linux kernel's TIPC subsystem was fixed by adding a node write lock around the node reset trace dump. The flaw allowed a trace event to access a freed link pointer, causing a kernel memory safety issue detected by KASAN.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99246 (opens in a new tab)
- git.kernel.org/stable/c/6abd93d01b0f495f29201925a5ee8e6a583c4044 (opens in a new tab)
- git.kernel.org/stable/c/6e492cb98ca69cc1145175e23e22e3b84da7f26d (opens in a new tab)
- git.kernel.org/stable/c/7bb6a35bd6d69019539d8782fb590fd2aa8a3236 (opens in a new tab)
- git.kernel.org/stable/c/a6101d62ccfa153db8c218ce59362b8e0316fd4f (opens in a new tab)
- git.kernel.org/stable/c/b8b7d28dc2b7472ffd1eff3954c38f1976b21a7b (opens in a new tab)
- git.kernel.org/stable/c/c8b72ca0918e95f708f67c8b3e69b05290f2b6d2 (opens in a new tab)
- git.kernel.org/stable/c/dddf197f29ba5e47a476dde82bf542ca2e0d5e5e (opens in a new tab)
- git.kernel.org/stable/c/fa8c78c0e49aa11fae116fd841e41aa8f2d68751 (opens in a new tab)