CVE-2026-52973
Summary
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.
Impact & exploitability
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected products we track (1)
Recommendation
Apply the vendor fix promptly. Open any affected product above for its exact safe version.
Official patch: https://git.kernel.org/stable/c/1dcd36420af2da5bd59306dba9caf78e3d248b1d ↗
Additional information
- NVD record
- https://git.kernel.org/stable/c/1dcd36420af2da5bd59306dba9caf78e3d248b1dPatch
- https://git.kernel.org/stable/c/974ac49a9a068b0591a59f65c63eb06579a13091Patch
- https://git.kernel.org/stable/c/ee9dce44362b2d8132c32964656ab6dff7dfbc6aPatch
- https://access.redhat.com/errata/RHSA-2026:45114
- https://access.redhat.com/errata/RHSA-2026:47040
- https://access.redhat.com/errata/RHSA-2026:62640
- https://access.redhat.com/errata/RHSA-2026:62642
- https://access.redhat.com/security/cve/CVE-2026-52973Advisory