migrate: correct lock ordering for hugetlb file folios
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Linux | Linux | unaffected |
|
||||||||||||||||||||||||||||||
| Linux | Linux | affected |
|
Configuration 1 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-4475-1 | linux security update |
Debian DLA |
DLA-4476-1 | linux-6.1 security update |
Debian DSA |
DSA-6126-1 | linux security update |
Debian DSA |
DSA-6127-1 | linux security update |
Ubuntu USN |
USN-8162-1 | Linux kernel (NVIDIA Tegra) vulnerabilities |
Ubuntu USN |
USN-8180-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-8180-2 | Linux kernel (FIPS) vulnerabilities |
Ubuntu USN |
USN-8186-1 | Linux kernel (Real-time) vulnerabilities |
Ubuntu USN |
USN-8187-1 | Linux kernel (NVIDIA) vulnerabilities |
Ubuntu USN |
USN-8188-1 | Linux kernel (HWE) vulnerabilities |
Ubuntu USN |
USN-8180-3 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-8180-4 | Linux kernel (Azure FIPS) vulnerabilities |
Ubuntu USN |
USN-8180-5 | Linux kernel (IBM) vulnerabilities |
Ubuntu USN |
USN-8243-1 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-8180-6 | Linux kernel (Raspberry Pi) vulnerabilities |
Ubuntu USN |
USN-8275-1 | Linux kernel (Xilinx ZynqMP) vulnerabilities |
Ubuntu USN |
USN-8278-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-8289-1 | Linux kernel (NVIDIA) vulnerabilities |
Ubuntu USN |
USN-8296-1 | Linux kernel (FIPS) vulnerabilities |
Ubuntu USN |
USN-8297-1 | Linux kernel (GCP) vulnerabilities |
Ubuntu USN |
USN-8296-2 | Linux kernel (NVIDIA Tegra) vulnerabilities |
Ubuntu USN |
USN-8278-2 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-8440-1 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-8499-1 | Linux kernel (Xilinx) vulnerabilities |
Ubuntu USN |
USN-8570-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-8594-1 | Linux kernel (OEM) vulnerabilities |
Ubuntu USN |
USN-8604-1 | Linux kernel (Azure) vulnerabilities |
Ubuntu USN |
USN-8605-1 | Linux kernel (Azure CVM) vulnerabilities |
Ubuntu USN |
USN-8570-2 | Linux kernel (Oracle) vulnerabilities |
Ubuntu USN |
USN-8289-2 | Linux kernel (NVIDIA) vulnerabilities |
Ubuntu USN |
USN-8393-1 | Linux kernel (Azure FIPS) vulnerabilities |
Ubuntu USN |
USN-8669-1 | Linux kernel (NVIDIA) vulnerabilities |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.107% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-362 |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | NVD-CWE-noinfo | |
| CPEs | cpe:2.3:o:linux:linux_kernel:5.10:-:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:5.10:rc4:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:5.10:rc5:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:5.10:rc6:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:5.10:rc7:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:* |
|
| Metrics |
cvssV3_1
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | migrate: correct lock ordering for hugetlb file folios | |
| First Time appeared |
Linux
Linux linux Kernel |
|
| CPEs | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Linux
Linux linux Kernel |
|
| References |
|