CVE-2026-52973
futex: Drop CLONE_THREAD requirement for private default hash alloc
- State
- Published
- Severity
- 7.8 High
- Published
- Jun 24, 2026
- Updated
- Oct 19, 2026
- Reserved
- Jun 9, 2026
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.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 3.1 | 7.8 High | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | Linux |
| 3.1 | 7.0 High | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H | redhat-SADP |
Weaknesses
- CWE-825 Expired Pointer Dereference
Affected Products
| Product | Versions |
|---|---|
LinuxLinux |
|
LinuxLinux |
|
References
- https://git.kernel.org/stable/c/1dcd36420af2da5bd59306dba9caf78e3d248b1d
- https://git.kernel.org/stable/c/974ac49a9a068b0591a59f65c63eb06579a13091
- https://git.kernel.org/stable/c/ee9dce44362b2d8132c32964656ab6dff7dfbc6a
- https://access.redhat.com/security/cve/CVE-2026-52973vdb-entry
- RHBZ#2492413issue-tracking
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-52973.json
- https://access.redhat.com/errata/RHSA-2026:45114vendor-advisory
- https://access.redhat.com/errata/RHSA-2026:47040vendor-advisory
- https://access.redhat.com/errata/RHSA-2026:62642vendor-advisory
- https://access.redhat.com/errata/RHSA-2026:62640vendor-advisory
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.