Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2026-53207

medium

In the Linux kernel, the following vulnerability has been resolved: mm/memory-failure: fix hugetlb_lock AA deadlock in get_huge_page_for_hwpoison Two concurr…

Vendor / product: Linux — linux kernel

In the Linux kernel, the following vulnerability has been resolved: mm/memory-failure: fix hugetlb_lock AA deadlock in get_huge_page_for_hwpoison Two concurrent madvise(MADV_HWPOISON) calls on the same hugetlb page can trigger a recursive spinlock self-deadlock (AA deadlock) on hugetlb_lock when racing with a concurrent unmap: thread#0 thread#1 -------- -------- madvise(folio, MADV_HWPOISON) -> poisons the folio successfully madvise(folio, MADV_HWPOISON) unmap(folio) try_memory_failure_hugetlb get_huge_page_for_hwpoison spin_lock_irq(&hugetlb_lock) MF_HUGETLB_FOLIO_PRE_POISONED goto out: folio_put() refcount: 1 -> 0 free_huge_folio() spin_lock_irqsave(&hugetlb_lock) -> AA DEADLOCK! The out: path in __get_huge_page_for_hwpoison() calls folio_put() to drop the GUP reference while the hugetlb_lock is still held by the hugetlb.c wrapper get_huge_page_for_hwpoison(). If concurrent unmap has released the page table mapping reference, folio_put() drops the folio refcount to zero, triggering free_huge_folio() which attempts to re-acquire the non-recursive hugetlb_lock. Fix this by moving hugetlb_lock acquisition from the hugetlb.c wrapper into get_huge_page_for_hwpoison(). Place spin_unlock_irq() before the folio_put() at the out: label so the folio is always released outside the lock. [akpm@linux-foundation.org: fix race, rename label per Miaohe]

CVSS
5.5
5.5 (CVSS v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2026-06-25 09:16
Modified: 2026-11-06 17:18
NVD status: Analyzed
Last synced 1 week ago
Verified against the source API 2026-11-06 17:46 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥5.15.54 <5.16, ≥5.18.1 <6.1.176, ≥6.2 <6.6.143, ≥6.7 <6.12.94, ≥6.13 <6.18.36, ≥6.19 <7.0.13

Weakness classification (CWE)

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/3c2d42b8ee345b17a4ba56b0f6492d1ff4c1178e
Patch / mitigation: https://git.kernel.org/stable/c/77b73b54801ae7137479c141fd0473a491c1dc48
Patch / mitigation: https://git.kernel.org/stable/c/a33bfed648c10f5a1519981dbfad80841191edc8
Patch / mitigation: https://git.kernel.org/stable/c/bf7ba8f96c258c30393814491930ae4ecdc5fe5e
Patch / mitigation: https://git.kernel.org/stable/c/dd77a83915b07e2b0205adb284f08b39ae31dc4b
Patch / mitigation: https://git.kernel.org/stable/c/fc3ff42cb0cbf947e4600ae9761c3783760050e2

References

Data sources

NVD CVE API 2.0 — fetched 2026-11-06 17:46 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs