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.

All Linux kernel installations are potentially impacted, regardless of vendor distribution. No specific kernel version range is supplied, so any kernel build that includes the buggy futex implementation without the patch may be vulnerable.

The absence of a CVSS or EPSS score signals that public severity metrics are not available. However, the nature of the bug—a use‑after‑free in kernel code—implies a high impact should an attacker be able to 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.