CVE-2026-52973

futex: Drop CLONE_THREAD requirement for private default hash alloc

Published Jun 24, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability originates in the Linux kernel’s futex subsystem, where the requirement for CLONE_THREAD was dropped for private default hash allocation. This change creates an unintended use‑after‑free condition in futex hash handling, as shown by a KASAN report indicating a slab use‑after‑free when a memory reference counter is freed. The weakness is a classic use‑after‑free, a type of memory corruption that can be exploited to read or write arbitrary kernel memory and thus elevate privileges, or to crash the system.

Affected Systems

All Linux kernel installations are potentially impacted, including versions 6.17 and 7.1 rc1 as specified in the CPE list. All other kernel builds that incorporate the buggy futex implementation without the patch may also be vulnerable.

Risk and Exploitability

The CVSS score of 7.8 indicates moderate to high severity. EPSS <1% and not listed in KEV, so the exploit likelihood is currently low, but the nature of the bug—a use‑after‑free in kernel code—implies a high impact if an attacker can trigger the flaw. The likely attack vector requires local execution with the ability to invoke clone() with CLONE_VM and CLONE_THREAD flags, suggesting that privileged or compromised local processes could exploit the weakness. Because this flaw can lead to arbitrary kernel code execution, the risk is considered significant until a patch is applied or mitigated.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the system to a Linux kernel release that contains the futex hash allocation fix.
  • Apply the patch manually by downloading the relevant commit from the provided git references and rebuilding the kernel if an automated update is not available.
  • If updating immediately is not possible, avoid or replace code that uses clone() with CLONE_VM and CLONE_THREAD flags, using vfork() instead where applicable.

Generated by OpenCVE AI on August 12, 2026 at 06:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8566-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8568-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8569-1 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-8593-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8663-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8664-1 Linux kernel (NVIDIA BaseOS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-3 Linux kernel (Oracle) vulnerabilities
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-825
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Important

Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
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.
Title futex: Drop CLONE_THREAD requirement for private default hash alloc
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 19, 2026, 7:47 PM
Reserved
Jun 9, 2026, 7:44 AM
Status
Modified
Published
Jun 24, 2026, 5:17 PM
Modified
Oct 19, 2026, 8:18 PM
Severity
Important
Public date
Jun 24, 2026, 12:00 AM