CVE-2026-53207
- Source
- https://cve.org/CVERecord?id=CVE-2026-53207
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53207.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-53207
- Downstream
AZL (1)
BELL (1)
CGA (13)
DEBIAN (1)
ECHO (1)
MGASA (1)
OESA (1)
openSUSE (1)
ROOT (3)
SUSE (10)
- Related
- Published
- 2026-06-25T08:39:13Z
- Modified
- 2026-10-20T12:00:32Z
- Summary
- mm/memory-failure: fix hugetlb_lock AA deadlock in get_huge_page_for_hwpoison
- Details
-
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) <- held __get_huge_page_for_hwpoison hugetlb_update_hwpoison() -> 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]
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53207.json" }- References
-
- https://git.kernel.org/stable/c/3c2d42b8ee345b17a4ba56b0f6492d1ff4c1178e
- https://git.kernel.org/stable/c/77b73b54801ae7137479c141fd0473a491c1dc48
- https://git.kernel.org/stable/c/a33bfed648c10f5a1519981dbfad80841191edc8
- https://git.kernel.org/stable/c/bf7ba8f96c258c30393814491930ae4ecdc5fe5e
- https://git.kernel.org/stable/c/dd77a83915b07e2b0205adb284f08b39ae31dc4b
- https://git.kernel.org/stable/c/fc3ff42cb0cbf947e4600ae9761c3783760050e2
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53207.json
- https://nvd.nist.gov/vuln/detail/CVE-2026-53207
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced405ce051236cc65b30bbfe490b28ce60ae6aed85Fixedfc3ff42cb0cbf947e4600ae9761c3783760050e2Fixed77b73b54801ae7137479c141fd0473a491c1dc48Fixeda33bfed648c10f5a1519981dbfad80841191edc8Fixeddd77a83915b07e2b0205adb284f08b39ae31dc4bFixedbf7ba8f96c258c30393814491930ae4ecdc5fe5eFixed3c2d42b8ee345b17a4ba56b0f6492d1ff4c1178e
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced5.15.54Fixed5.16
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced62d1655b922958826b7ec22682c3141746f75064
Affected versions
v5.*
Linux / Kernel
Package
- Name
- Kernel