GHSA-r4cc-8gxc-2cxh
A use-after-free (UAF) vulnerability in the Linux kernel's fhandle subsystem was fixed by adding proper RCU read locking around mount namespace access in may_decode_fh(). The flaw arises from concurrent unmounting and freeing of mount namespaces without synchronization, potentially leading to kernel crashes or infinite loops. This issue requires specific kernel configurations (CONFIG_PREEMPTION or CONFIG_RCU_STRICT_GRACE_PERIOD) to be exploitable and is considered to have limited security impact.
AI Analysis
Technical Summary
The Linux kernel contained a use-after-free vulnerability in the fhandle code path, specifically in the may_decode_fh() function, which accessed mount::mnt_ns without holding locks. This allowed a race condition where the mount point could be unmounted concurrently, and the mount namespace freed after an RCU grace period, leading to a use-after-free scenario. The fix involved adding rcu_read_lock() around mount::mnt_ns access and using WRITE_ONCE() for writers to prevent races with lockless readers. The vulnerability requires kernel configurations that enable preemption or strict RCU grace periods and is unlikely to be exploitable for significant security impact.
Potential Impact
The vulnerability could cause kernel crashes by dereferencing invalid memory, infinite loops, or leak minor information such as the result of an integer comparison to userspace. There is no indication of privilege escalation or remote code execution. The impact is limited to potential denial of service or minor information leakage under specific kernel configurations.
Mitigation Recommendations
A fix is available that adds proper RCU read locking around mount namespace access in the affected code. Users should apply the official Linux kernel patches that address this issue. Since this is a kernel-level race condition, upgrading to a patched kernel version is the recommended remediation. No additional mitigations are indicated.
GHSA-r4cc-8gxc-2cxh
Description
A use-after-free (UAF) vulnerability in the Linux kernel's fhandle subsystem was fixed by adding proper RCU read locking around mount namespace access in may_decode_fh(). The flaw arises from concurrent unmounting and freeing of mount namespaces without synchronization, potentially leading to kernel crashes or infinite loops. This issue requires specific kernel configurations (CONFIG_PREEMPTION or CONFIG_RCU_STRICT_GRACE_PERIOD) to be exploitable and is considered to have limited security impact.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel contained a use-after-free vulnerability in the fhandle code path, specifically in the may_decode_fh() function, which accessed mount::mnt_ns without holding locks. This allowed a race condition where the mount point could be unmounted concurrently, and the mount namespace freed after an RCU grace period, leading to a use-after-free scenario. The fix involved adding rcu_read_lock() around mount::mnt_ns access and using WRITE_ONCE() for writers to prevent races with lockless readers. The vulnerability requires kernel configurations that enable preemption or strict RCU grace periods and is unlikely to be exploitable for significant security impact.
Potential Impact
The vulnerability could cause kernel crashes by dereferencing invalid memory, infinite loops, or leak minor information such as the result of an integer comparison to userspace. There is no indication of privilege escalation or remote code execution. The impact is limited to potential denial of service or minor information leakage under specific kernel configurations.
Mitigation Recommendations
A fix is available that adds proper RCU read locking around mount namespace access in the affected code. Users should apply the official Linux kernel patches that address this issue. Since this is a kernel-level race condition, upgrading to a patched kernel version is the recommended remediation. No additional mitigations are indicated.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-r4cc-8gxc-2cxh
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53341"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a498a7327e9c7971936ea06
Added to database: 07/04/2026, 22:34:27 UTC
Last enriched: 07/04/2026, 23:07:58 UTC
Last updated: 07/05/2026, 00:51:17 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.