mm/hugetlb: avoid corrupting page->mapping in hugetlb_mcopy_atomic_pte
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
5.15.655.19.66.0In the Linux kernel, the following vulnerability has been resolved:
mm/hugetlb: avoid corrupting page->mapping in hugetlb_mcopy_atomic_pte
In MCOPY_ATOMIC_CONTINUE case with a non-shared VMA, pages in the page cache are installed in the ptes. But hugepage_add_new_anon_rmap is called for them mistakenly because they're not vm_shared. This will corrupt the page->mapping used by page cache code.
From the CVE record · Linux
The Linux kernel can corrupt a page-cache page’s mapping in hugetlb_mcopy_atomic_pte. This occurs when MCOPY_ATOMIC_CONTINUE installs page-cache pages into a non-shared VMA and mistakenly calls hugepage_add_new_anon_rmap. The input does not specify attacker access requirements or user interaction.
Engineers running the Linux kernel should check their versions against the vendor advisory; affected versions are not specified in the input.