CVE-2026-52973 Details
Description
In the Linux kernel, the following vulnerability has been resolved: futex: Drop CLONE_THREAD requirement for private default hash alloc Currently need_futex_hash_allocate_default() depends on strict pthread semantics, abusing CLONE_THREAD. This breaks the non-concurrency assumptions when doing the mm->futex_ref pcpu allocations, leading to bugs[0] when sharing the mm in other ways; ie: BUG: KASAN: slab-use-after-free in futex_hash_put ... where the +1 bias can end up on a percpu counter that mm->futex_ref no longer points at. Loosen the check to cover any CLONE_VM clone, except vfork(). Excluding vfork keeps the existing paths untouched (no overhead), and we can't race in the first place: either the parent is suspended and the child runs alone, or mm->futex_ref is already allocated from an earlier CLONE_VM.
A vulnerability in the Linux kernel's handling of futex hash allocations has been addressed. The issue arose because the function need_futex_hash_allocate_default() relied on strict pthread semantics, improperly using CLONE_THREAD. This dependency disrupted the non-concurrency assumptions during per-CPU allocations for the futex reference, leading to a use-after-free bug when the memory management was shared in other ways. The vulnerability was caused by the CLONE_THREAD requirement, which has now been relaxed to apply only to certain cloning scenarios, allowing for a more stable and error-free allocation process.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://access.redhat.com/errata/RHSA-2026:45114 | redhat-SADP | |
| https://access.redhat.com/errata/RHSA-2026:47040 | redhat-SADP | |
| https://access.redhat.com/errata/RHSA-2026:62640 | redhat-SADP | |
| https://access.redhat.com/errata/RHSA-2026:62642 | redhat-SADP | |
| https://access.redhat.com/security/cve/CVE-2026-52973 | redhat-SADP | Third Party Advisory |
| https://bugzilla.redhat.com/show_bug.cgi?id=2492413 | redhat-SADP | Issue TrackingThird Party Advisory |
| https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-52973.json | redhat-SADP | Third Party Advisory |
| https://git.kernel.org/stable/c/1dcd36420af2da5bd59306dba9caf78e3d248b1d | kernel.org | Patch |
| https://git.kernel.org/stable/c/974ac49a9a068b0591a59f65c63eb06579a13091 | kernel.org | Patch |
| https://git.kernel.org/stable/c/ee9dce44362b2d8132c32964656ab6dff7dfbc6a | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-416 | Use After Free | [email protected] |
| CWE-825 | Expired Pointer Dereference | redhat-SADP |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.17.1, < 6.18.33 >= 6.19, < 7.0.10 6.17 - 6.17 rc5 6.17 rc6 6.17 rc7 7.1 rc1 |
CPE
Remediation
| |
Change History
10 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 3, 2026 | CVE Modified | kernel.org |
| Sep 3, 2026 | CVE Modified | redhat-SADP |
| Jul 29, 2026 | CVE Modified | redhat-SADP |
| Jul 27, 2026 | CVE Modified | redhat-SADP |
| Jul 15, 2026 | CVE Modified | redhat-SADP |
| Jul 14, 2026 | Initial Analysis | [email protected] |
| Jul 9, 2026 | CVE Modified | redhat-SADP |
| Jun 30, 2026 | CVE Modified | redhat-SADP |
| Jun 28, 2026 | CVE Modified | kernel.org |
| Jun 24, 2026 | New CVE Received | kernel.org |