{"id":"CVE-2026-53154","summary":"mm/hugetlb: restore reservation on error in hugetlb folio copy paths","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nmm/hugetlb: restore reservation on error in hugetlb folio copy paths\n\nTwo sites in mm/hugetlb.c allocate a hugetlb folio via\nalloc_hugetlb_folio() (consuming a VMA reservation) and then call\ncopy_user_large_folio(), which became int-returning in commit 1cb9dc4b475c\n(\"mm: hwpoison: support recovery from HugePage copy-on-write faults\") and\ncan now fail (e.g.  -EHWPOISON on a hwpoisoned source page).  On the\nfailure path, folio_put() restores the global hugetlb pool count through\nfree_huge_folio(), but the per-VMA reservation map entry is left marked\nconsumed:\n\n  - hugetlb_mfill_atomic_pte() resubmission path (UFFDIO_COPY)\n  - copy_hugetlb_page_range() fork-time CoW path when\n    hugetlb_try_dup_anon_rmap() fails (rare: pinned hugetlb anon\n    folio under fork)\n\nUser-visible effect: on UFFDIO_COPY into a private hugetlb VMA where the\nresubmission copy fails, the reservation for that address is leaked from\nthe VMA's reserve map.  A subsequent fault at the same address takes the\nno-reservation path, and under hugetlb pool pressure the task is SIGBUSed\nat an address it had previously reserved.  The fork-time CoW path leaks\nthe same way in the child VMA's reserve map, though it requires the much\nrarer combination of pinned hugetlb anon page + hwpoisoned source.\n\nAdd the missing restore_reserve_on_error() call before folio_put() on both\nerror paths.","modified":"2026-07-09T03:51:14.533672411Z","published":"2026-06-25T08:38:38.168Z","related":["CGA-g693-hmr2-27gh"],"database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53154.json"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/40c81856e622a9dc59294a90d169ac07ea25b0b0"},{"type":"WEB","url":"https://git.kernel.org/stable/c/45e33d43243d71d089af42f5077b8213cee6610f"},{"type":"WEB","url":"https://git.kernel.org/stable/c/8d6e1dd3ad1340cd8b6d554b7aa93d8f0a1c6d38"},{"type":"WEB","url":"https://git.kernel.org/stable/c/c72469ac0f274bde3f0df60a4584e14a123d0aa6"},{"type":"WEB","url":"https://git.kernel.org/stable/c/e47bf16af3c45470ea32f2241fa69aefe0dd61bd"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53154.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53154"},{"type":"PACKAGE","url":"https://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":[{"introduced":"1cb9dc4b475c7418f925ab0c97b6750007d9f52e"},{"fixed":"8d6e1dd3ad1340cd8b6d554b7aa93d8f0a1c6d38"},{"fixed":"e47bf16af3c45470ea32f2241fa69aefe0dd61bd"},{"fixed":"c72469ac0f274bde3f0df60a4584e14a123d0aa6"},{"fixed":"45e33d43243d71d089af42f5077b8213cee6610f"},{"fixed":"40c81856e622a9dc59294a90d169ac07ea25b0b0"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53154.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.4.0"},{"fixed":"6.6.143"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.94"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.36"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.0.13"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53154.json"}}],"schema_version":"1.7.5"}