This kernel bug allows two concurrent madvise(MADV_HWPOISON) calls on the same hugetlb page to trigger a recursive spinlock self-deadlock on hugetlb_lock when a concurrent unmap races. The deadlock stalls the kernel and can disrupt service availability, but it does not directly enable code execution or confidentiality compromise. The vulnerability arises from improper lock ordering in get_huge_page_for_hwpoison and results in a self-deadlock that can affect all processes sharing the page.

All Linux kernel releases that include the pre-fix code path are affected, as the CPE list indicates the entire Linux kernel and no specific version range is provided. The vulnerability exists in the mainline kernel source before the commit that fixed the lock acquisition logic. Users of any distribution using kernels older than the latest patch are potentially exposed.

The CVSS score is not provided and the EPSS score is unavailable, but the vulnerability is not listed in the CISA KEV catalog. Because the flaw requires privileged kernel access to trigger madvise(MADV_HWPOISON) and unmap operations, the most likely attack vector is local or requires root privileges. An attacker with sufficient permissions could cause a kernel hang that may lead to service disruption, but the vulnerability does not provide a direct path for remote code execution or data exfiltration. The lack of public exploitation evidence suggests a lower exploitation probability, though the impact on availability is significant if exploited.