CVE-2026-52973futex: Drop CLONE_THREAD requirement for private default hash alloc
Updated under an hour ago ()
Does this affect you?
It affects Linux and 2 other products. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- CWE-825
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Modified
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from d9b05321e21e4b218de4ce8a590bf375f58b6346 before 1dcd36420af2da5bd59306dba9caf78e3d248b1d; from d9b05321e21e4b218de4ce8a590bf375f58b6346 before 974ac49a9a068b0591a59f65c63eb06579a13091; from d9b05321e21e4b218de4ce8a590bf375f58b6346 before ee9dce44362b2d8132c32964656ab6dff7dfbc6a | CNA record |
Red Hat Red Hat Enterprise Linux 10 redhat:enterprise_linux | from 0:6.12.0-211.39.1.el10_2 not affected | CISA ADP |
linux linux_kernel linux:linux_kernel | from 6.17.1 before 6.18.33; from 6.19 before 7.0.10; 6.17; 6.17; 6.17; 6.17; 7.1 | NVD |
References
- 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-52973third-party-advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2492413issue-tracking, third-party-advisory
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-52973.jsonthird-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.