PT-2026-51867 · Linux · Linux
Published
2026-06-24
·
Updated
2026-06-24
·
CVE-2026-52973
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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.
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux