A race can arise during futex wait‑requeue‑PI and requeue‑PI when a task leaves early due to a signal or timeout while another higher‑priority task holds the futex. The leaving task cannot remove itself from the wait queue because it cannot acquire the required hold‑bucket lock; it blocks, and the other task busy‑loops trying to re‑queue, resulting in a live‑lock that stalls system progress. The impact is a denial of service at the kernel level, preventing all tasks from continuing and potentially freezing the system. The weakness is a concurrency race involving improper lock handling.

Affected product: Linux kernel. The vendor is Linux, and the product is the kernel as a whole. Specific affected kernel versions are not listed in the provided data, so any kernel build that includes the unfixed futex implementation before the commit that fixes the issue may be vulnerable.

The CVSS score is not available, so the severity is unspecified. EPSS exploitation probability is also not reported, and the vulnerability is not listed in the CISA KEV catalog. Based on the description, the most likely attack vector is local kernel exploitation, requiring the attacker to trigger a futex requeue while holding a higher‑priority task. Because the flaw leads to a livelock that can lock up the whole system, the potential impact is high. The lack of official metrics suggests careful monitoring of kernel updates and awareness of the underlying concurrency weakness.