Skip to main content

In the Linux kernel, the following vulnerability has been resolved: tipc: hold a reference to nodes found by link name tipc_node_find_by_name()… (CVE-2026-99053)

0
High
Published: 10/23/2026 (10/23/2026, 15:31:36 UTC)
Source: GCVE Database

Description

A use-after-free vulnerability in the Linux kernel's TIPC subsystem was resolved. The function tipc_node_find_by_name() returned a node pointer after dropping its RCU read lock without taking a reference, leading to a race condition where handlers could access a freed node. This could cause kernel memory corruption and instability. The issue was detected by KASAN and fixed by acquiring a reference to the node before leaving the RCU read lock and releasing it appropriately after use.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/23/2026, 18:52:02 UTC

Technical Analysis

The Linux kernel's TIPC subsystem had a vulnerability where tipc_node_find_by_name() returned a node pointer after releasing its RCU read lock without incrementing the node's reference count. This allowed concurrent operations, such as LINK_SET, LINK_GET, and LINK_RESET_STATS handlers, to access a node that might have been freed by a timer-driven cleanup routine (tipc_node_timeout). The race condition could lead to use-after-free scenarios, causing kernel memory corruption. The fix involved acquiring a reference to the node with kref_get_unless_zero() before leaving the RCU read lock and releasing that reference after the last access, including during packet transmission in LINK_SET. This preserves the existing locking and error handling order while preventing use-after-free.

Potential Impact

The vulnerability could lead to kernel memory corruption due to use-after-free conditions in the TIPC subsystem. This can cause system instability, crashes, or potential privilege escalation if exploited. No known exploits in the wild have been reported.

Mitigation Recommendations

A fix has been implemented in the Linux kernel that ensures a reference is held on nodes returned by tipc_node_find_by_name() before leaving the RCU read lock, preventing use-after-free. Users should update to the fixed kernel version once available. No additional mitigation steps are indicated.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-j7x4-wphj-g9x9
Osv Schema Version
1.4.0
Aliases
["CVE-2026-99053"]

Threat ID: 6adbaaced73cc49347b2051d

Added to database: 10/23/2026, 18:43:26 UTC

Last enriched: 10/23/2026, 18:52:02 UTC

Last updated: 10/24/2026, 00:25:11 UTC

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses