CVE-2026-99246: tipc: protect node reset trace dump with node lock
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.44% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 6abd93d01b0f495f29201925a5ee8e6a583c4044, 6e492cb98ca69cc1145175e23e22e3b84da7f26d, 7bb6a35bd6d69019539d8782fb590fd2aa8a3236.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 6abd93d01b0f495f29201925a5ee8e6a583c4044, 6e492cb98ca69cc1145175e23e22e3b84da7f26d, 7bb6a35bd6d69019539d8782fb590fd2aa8a3236 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 3, 2026
- Updated
- Nov 3, 2026
- EPSS
- 0.4% · 38th percentile
- CWE
- —
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.0affected
- eb18a510b5cd4daeb9736ad8db57a9fc49db185b and later · before c8b72ca0918e95f708f67c8b3e69b05290f2b6d2affected · git
- eb18a510b5cd4daeb9736ad8db57a9fc49db185b and later · before 6e492cb98ca69cc1145175e23e22e3b84da7f26daffected · git
- eb18a510b5cd4daeb9736ad8db57a9fc49db185b and later · before 7bb6a35bd6d69019539d8782fb590fd2aa8a3236affected · git
- eb18a510b5cd4daeb9736ad8db57a9fc49db185b and later · before 6abd93d01b0f495f29201925a5ee8e6a583c4044affected · git
- eb18a510b5cd4daeb9736ad8db57a9fc49db185b and later · before a6101d62ccfa153db8c218ce59362b8e0316fd4faffected · git
- eb18a510b5cd4daeb9736ad8db57a9fc49db185b and later · before b8b7d28dc2b7472ffd1eff3954c38f1976b21a7baffected · git
- eb18a510b5cd4daeb9736ad8db57a9fc49db185b and later · before fa8c78c0e49aa11fae116fd841e41aa8f2d68751affected · git
- eb18a510b5cd4daeb9736ad8db57a9fc49db185b and later · before dddf197f29ba5e47a476dde82bf542ca2e0d5e5eaffected · git
- before 5.0not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.115-1 | 6.12.115-1 |
| Debian:14 | linux | before 7.2.13-1 | 7.2.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-99244Nov 3, 2026 · pid_namespace: prevent TIF_NOTIFY_SIGNAL from interrupting the reaper0Monitor
- ← EarlierCVE-2026-99245Nov 3, 2026 · KEYS: Fix key_reject_and_link() race with keyring restriction0Monitor
- Later →CVE-2026-99247Nov 3, 2026 · tracing: Do not initialize tracefs work if tracing is disabled0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 6abd93d01b0f495f29201925a5ee8e6a583c4044 | Vendor (CNA) |
| Linux Linux | 6e492cb98ca69cc1145175e23e22e3b84da7f26d | Vendor (CNA) |
| Linux Linux | 7bb6a35bd6d69019539d8782fb590fd2aa8a3236 | Vendor (CNA) |
| Linux Linux | a6101d62ccfa153db8c218ce59362b8e0316fd4f | Vendor (CNA) |
| Linux Linux | b8b7d28dc2b7472ffd1eff3954c38f1976b21a7b | Vendor (CNA) |
| Linux Linux | c8b72ca0918e95f708f67c8b3e69b05290f2b6d2 | Vendor (CNA) |
| Linux Linux | dddf197f29ba5e47a476dde82bf542ca2e0d5e5e | Vendor (CNA) |
| Linux Linux | fa8c78c0e49aa11fae116fd841e41aa8f2d68751 | Vendor (CNA) |
| debian:linux | 6.12.115-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 10, 2026+7 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1451 · Nov 4, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- CVSS— → 8.1
- Severity— → high
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/6e492cb98ca69cc1145175e23e22e3b84da7f26d
- git.kernel.org/stable/c/7bb6a35bd6d69019539d8782fb590fd2aa8a3236
- git.kernel.org/stable/c/a6101d62ccfa153db8c218ce59362b8e0316fd4f
- git.kernel.org/stable/c/b8b7d28dc2b7472ffd1eff3954c38f1976b21a7b
- git.kernel.org/stable/c/c8b72ca0918e95f708f67c8b3e69b05290f2b6d2
- git.kernel.org/stable/c/dddf197f29ba5e47a476dde82bf542ca2e0d5e5e
- git.kernel.org/stable/c/fa8c78c0e49aa11fae116fd841e41aa8f2d68751
Vendor advisories and official records. Exploit/PoC links are deliberately left out.