In the Linux kernel, the following vulnerability has been resolved: futex: Drop CLONE_THREAD requirement for private default hash alloc Currently… (CVE-2026-52973)
A vulnerability in the Linux kernel futex subsystem related to the CLONE_THREAD requirement for private default hash allocation has been resolved. The issue involved incorrect assumptions about concurrency when sharing memory mappings (mm) in ways other than pthread semantics, leading to use-after-free bugs. This could cause kernel memory corruption and crashes. The vulnerability has been addressed by loosening the check to cover any CLONE_VM clone except vfork, preventing the race conditions. Red Hat has released security updates for Red Hat Enterprise Linux 9 and 10 to fix this issue. The updates require system reboot to take effect.
AI Analysis
Technical Summary
The Linux kernel futex subsystem had a vulnerability where the function need_futex_hash_allocate_default() depended strictly on the CLONE_THREAD flag for private default hash allocation. This strict dependency violated non-concurrency assumptions during mm->futex_ref per-CPU allocations, causing use-after-free bugs (e.g., KASAN slab-use-after-free in futex_hash_put) when the memory descriptor (mm) was shared in ways other than pthread semantics. The fix broadens the check to include any CLONE_VM clone except vfork, maintaining existing performance paths while preventing race conditions and reference count errors. This vulnerability is tracked as CVE-2026-52973 and has been addressed in Red Hat Enterprise Linux kernel updates for versions 9.8 and 10.2 across multiple architectures.
Potential Impact
The vulnerability can lead to use-after-free conditions in the kernel futex subsystem, resulting in potential memory corruption. The CVSS vector indicates high impact on confidentiality, integrity, and availability (C:H/I:H/A:H), meaning exploitation could allow an attacker with local privileges to cause system crashes, data corruption, or potentially escalate privileges. No known exploits in the wild have been reported. The issue affects kernel stability and security on affected Red Hat Enterprise Linux systems.
Mitigation Recommendations
Official patches fixing this vulnerability are available from Red Hat for Red Hat Enterprise Linux versions 9.8 and 10.2. Users should apply the kernel updates provided in advisories RHSA-2026:45114 and RHSA-2026:47040 and reboot affected systems to ensure the fix takes effect. There are no vendor advisories indicating that no action is required; therefore, applying the official updates is the recommended mitigation.
In the Linux kernel, the following vulnerability has been resolved: futex: Drop CLONE_THREAD requirement for private default hash alloc Currently… (CVE-2026-52973)
Description
A vulnerability in the Linux kernel futex subsystem related to the CLONE_THREAD requirement for private default hash allocation has been resolved. The issue involved incorrect assumptions about concurrency when sharing memory mappings (mm) in ways other than pthread semantics, leading to use-after-free bugs. This could cause kernel memory corruption and crashes. The vulnerability has been addressed by loosening the check to cover any CLONE_VM clone except vfork, preventing the race conditions. Red Hat has released security updates for Red Hat Enterprise Linux 9 and 10 to fix this issue. The updates require system reboot to take effect.
CVSS v3.1
Score 7.8high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel futex subsystem had a vulnerability where the function need_futex_hash_allocate_default() depended strictly on the CLONE_THREAD flag for private default hash allocation. This strict dependency violated non-concurrency assumptions during mm->futex_ref per-CPU allocations, causing use-after-free bugs (e.g., KASAN slab-use-after-free in futex_hash_put) when the memory descriptor (mm) was shared in ways other than pthread semantics. The fix broadens the check to include any CLONE_VM clone except vfork, maintaining existing performance paths while preventing race conditions and reference count errors. This vulnerability is tracked as CVE-2026-52973 and has been addressed in Red Hat Enterprise Linux kernel updates for versions 9.8 and 10.2 across multiple architectures.
Potential Impact
The vulnerability can lead to use-after-free conditions in the kernel futex subsystem, resulting in potential memory corruption. The CVSS vector indicates high impact on confidentiality, integrity, and availability (C:H/I:H/A:H), meaning exploitation could allow an attacker with local privileges to cause system crashes, data corruption, or potentially escalate privileges. No known exploits in the wild have been reported. The issue affects kernel stability and security on affected Red Hat Enterprise Linux systems.
Mitigation Recommendations
Official patches fixing this vulnerability are available from Red Hat for Red Hat Enterprise Linux versions 9.8 and 10.2. Users should apply the kernel updates provided in advisories RHSA-2026:45114 and RHSA-2026:47040 and reboot affected systems to ensure the fix takes effect. There are no vendor advisories indicating that no action is required; therefore, applying the official updates is the recommended mitigation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-9qj4-wr4g-7m6f
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-52973"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6ae5599c2644c7f89a94f8
Added to database: 07/30/2026, 05:47:05 UTC
Last enriched: 07/30/2026, 07:27:16 UTC
Last updated: 07/31/2026, 19:24:47 UTC
Views: 11
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.