{"id":5367,"date":"2026-09-04T18:47:47","date_gmt":"2026-09-04T10:47:47","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-68163"},"modified":"2026-09-04T18:47:47","modified_gmt":"2026-09-04T10:47:47","slug":"cve-2026-68163","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-68163","title":{"rendered":"CVE-2026-68163 [HIGH] &#8211; In the Linux kernel, the following vulnerability has been resolved:\n\nmm\/page_vma_mapped: f"},"content":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>mm\/page_vma_mapped: fix device-private PMD handling<\/p>\n<p>Commit 65edfda6f3f2 (&#8220;mm\/rmap: extend rmap and migration support<br \/>\ndevice-private entries&#8221;) introduced the concept of device-private PMD<br \/>\nentries, but did not correctly update the rmap walk code to account for<br \/>\nthem.<\/p>\n<p>As a result, when page_vma_mapped_walk() encounters device-private PMD<br \/>\nentries, it takes no action other than to acquire the PMD lock and exit.<\/p>\n<p>However this is highly problematic for two reasons &#8211; firstly, device<br \/>\nprivate entries possess a PFN so check_pmd() needs to be called to ensure<br \/>\nan overlapping PFN range.<\/p>\n<p>Secondly, and more importantly, if PVMW_MIGRATION is set the caller<br \/>\nassumes the returned entry is a migration entry, resulting in memory<br \/>\ncorruption when the caller tries to interpret the device private entry as<br \/>\nsuch.<\/p>\n<p>In addition, commit 146287290023 (&#8220;mm\/huge_memory: implement<br \/>\ndevice-private THP splitting&#8221;) allowed device private PMDs to be split<br \/>\nlike THP mappings, but again did not update this code path.<\/p>\n<p>As a result, we might race a PMD split prior to acquiring the PMD lock.<\/p>\n<p>This patch addresses all of these issues by invoking check_pmd(), ensuring<br \/>\nPMVW_MIGRATION is not set and checks whether a split raced us we do for<br \/>\nPMD THP and migration entries.<\/p>\n<p>Instead of checking for a subset of the cases after taking the pmd_lock(),<br \/>\nput device-private along with pmd_trans_huge() and<br \/>\npmd_is_migration_entry().  Also remove thp_migration_supported() as it is<br \/>\nalready guarded by pmd_is_migration_entry().<\/p>\n<p>[akpm@linux-foundation.org: fix Raspberry Pi 1 build, per David]<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the Linux kernel, the following vulnerability has been resolved:<\/p>\n<p>mm\/page_vma_mapped: fix device-private PMD handling<\/p>\n<p>Commit 65edfda6f3f2 (&#8220;mm\/rmap: extend rmap and migration support<br \/>\ndevice-privat<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-5367","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/5367","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=5367"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=5367"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=5367"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}