mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 39dde65c9940c97fcd178a3d2b1c57ed8b7b68aa · < a6bfeb97941a9187833b526bc6cc4ff5706d0ce9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race
huge_pmd_unshare() drops a reference on a page table that may have previously been shared across processes, potentially turning it into a normal page table used in another process in which unrelated VMAs can afterwards be installed.
If this happens in the middle of a concurrent gup_fast(), gup_fast() could end up walking the page tables of another process. While I don't see any way in which that immediately leads to kernel memory corruption, it is really weird and unexpected.
Fix it with an explicit broadcast IPI through tlb_remove_table_sync_one(), just like we do in khugepaged when removing page tables for a THP collapse.
From the CVE record · Linux
A race between huge_pmd_unshare() and concurrent GUP-fast in the Linux kernel can cause GUP-fast to walk another process’s page tables. The description does not establish a way to exploit this for kernel memory corruption or specify authentication or user-interaction requirements.
Anyone running the Linux kernel should check whether their version includes the hugetlb fix; affected versions are not specified.