In the Linux kernel, the following vulnerability has been resolved: migrate: correct lock ordering for hugetlb file folios Syzbot has found a deadlock (analyzed by Lance Yang): 1) Task (5749): Holds folio_lock, then tries to acquire i_mmap_rwsem(read lock). 2) Task (5754): Holds i_mmap_rwsem(write lock), then tries to acquire folio_lock. migrate_pages() -> migrate_hugetlbs() -> unmap_and_move_huge_page() <- Takes folio_lock! -> remove_migration_ptes() -> __rmap_walk_file() -> i_mmap_lock_read() <- Waits for i_mmap_rwsem(read lock)! hugetlbfs_fallocate() -> hugetlbfs_punch_hole() <- Takes i_mmap_rwsem(write lock)! -> hugetlbfs_zero_partial_page() -> filemap_lock_hugetlb_folio() -> filemap_lock_folio() -> __filemap_get_folio <- Waits for folio_lock! The migration path is the one taking locks in the wrong order according to the documentation at the top of mm/rmap.c. So expand the scope of the existing i_mmap_lock to cover the calls to remove_migration_ptes() too. This is (mostly) how it used to be after commit c0d0381ade79. That was removed by 336bf30eb765 for both file & anon hugetlb pages when it should only have been removed for anon hugetlb pages.
Upstream advisory: https://lore.kernel.org/linux-cve-announce/2026020427-CVE-2026-23097-a591@gregkh/T
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:3463 https://access.redhat.com/errata/RHSA-2026:3463
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2026:3464 https://access.redhat.com/errata/RHSA-2026:3464
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2026:3488 https://access.redhat.com/errata/RHSA-2026:3488
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2026:4012 https://access.redhat.com/errata/RHSA-2026:4012
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Extended Update Support Via RHSA-2026:10108 https://access.redhat.com/errata/RHSA-2026:10108
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.6 Extended Update Support Via RHSA-2026:11313 https://access.redhat.com/errata/RHSA-2026:11313
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions Red Hat Enterprise Linux 8.6 Telecommunications Update Service Via RHSA-2026:13664 https://access.redhat.com/errata/RHSA-2026:13664
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions Red Hat Enterprise Linux 8.8 Telecommunications Update Service Via RHSA-2026:13681 https://access.redhat.com/errata/RHSA-2026:13681
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions Via RHSA-2026:13734 https://access.redhat.com/errata/RHSA-2026:13734
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions Via RHSA-2026:13936 https://access.redhat.com/errata/RHSA-2026:13936
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions Via RHSA-2026:14137 https://access.redhat.com/errata/RHSA-2026:14137
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions Via RHSA-2026:14301 https://access.redhat.com/errata/RHSA-2026:14301
This issue has been addressed in the following products: Red Hat Enterprise Linux 10.0 Extended Update Support Via RHSA-2026:15883 https://access.redhat.com/errata/RHSA-2026:15883