Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

In the Linux kernel, the following vulnerability has been resolved: tipc: read le->link under the node lock in tipc_node_link_down()… (CVE-2026-74609)

0
High
Published: 08/22/2026 (08/22/2026, 18:30:26 UTC)
Source: GCVE Database

Description

A use-after-free vulnerability in the Linux kernel's TIPC subsystem was resolved by moving a pointer read inside a lock to prevent concurrent access to freed memory. The flaw involved dereferencing a link pointer without proper synchronization, leading to potential memory corruption. This issue was fixed by ensuring the pointer is accessed only while holding the node lock, preventing race conditions between link usage and deletion.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/22/2026, 23:11:14 UTC

Technical Analysis

The vulnerability in the Linux kernel's TIPC subsystem (CVE-2026-74609) arises because tipc_node_link_down() caches a pointer to a link structure (le->link) before acquiring the node lock. This pointer can be freed concurrently by another CPU under the node lock, causing a use-after-free condition when the first CPU dereferences the stale pointer. The flaw allows both use-after-free reads and writes in functions tipc_link_is_establishing() and tipc_link_reset(). The fix moves the read of le->link inside the tipc_node_write_lock() critical section, ensuring serialization against concurrent frees and preventing dereferencing freed memory.

Potential Impact

The vulnerability causes use-after-free conditions in the kernel, which can lead to memory corruption and potential kernel crashes or undefined behavior. However, no known exploits in the wild have been reported. The impact is limited to kernel stability and security due to unsafe memory access in the TIPC networking code.

Mitigation Recommendations

A fix is available that moves the read of the link pointer inside the node lock to prevent race conditions. Users should apply the official Linux kernel patches that address CVE-2026-74609. Since this is a kernel-level issue, upgrading to a patched kernel version is the recommended remediation. No additional mitigations 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-c6xm-fh9c-399h
Osv Schema Version
1.4.0
Aliases
["CVE-2026-74609"]
Ecosystems
[]
Database Specific Severity
null
Cvss Version
null

Threat ID: 6a8a27f3acd9273b499bc88c

Added to database: 08/22/2026, 22:51:31 UTC

Last enriched: 08/22/2026, 23:11:14 UTC

Last updated: 08/23/2026, 00:10:43 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