summaryrefslogtreecommitdiffstats
path: root/mm/page_table_check.c
diff options
context:
space:
mode:
authorRuihan Li <lrh2000@pku.edu.cn>2023-05-15 21:09:57 +0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2023-05-29 16:14:28 +0100
commit81a31a860bb61d54eb688af2568d9332ed9b8942 (patch)
treea34c1ac8fb3f3814f3b596d74e4561bac35c99b4 /mm/page_table_check.c
parentd0b861653f8c16839c3035875b556afc4472f941 (diff)
downloadlinux-81a31a860bb61d54eb688af2568d9332ed9b8942.tar.gz
linux-81a31a860bb61d54eb688af2568d9332ed9b8942.tar.bz2
linux-81a31a860bb61d54eb688af2568d9332ed9b8942.zip
mm: page_table_check: Make it dependent on EXCLUSIVE_SYSTEM_RAM
Without EXCLUSIVE_SYSTEM_RAM, users are allowed to map arbitrary physical memory regions into the userspace via /dev/mem. At the same time, pages may change their properties (e.g., from anonymous pages to named pages) while they are still being mapped in the userspace, leading to "corruption" detected by the page table check. To avoid these false positives, this patch makes PAGE_TABLE_CHECK depends on EXCLUSIVE_SYSTEM_RAM. This dependency is understandable because PAGE_TABLE_CHECK is a hardening technique but /dev/mem without STRICT_DEVMEM (i.e., !EXCLUSIVE_SYSTEM_RAM) is itself a security problem. Even with EXCLUSIVE_SYSTEM_RAM, I/O pages may be still allowed to be mapped via /dev/mem. However, these pages are always considered as named pages, so they won't break the logic used in the page table check. Cc: <stable@vger.kernel.org> # 5.17 Signed-off-by: Ruihan Li <lrh2000@pku.edu.cn> Acked-by: David Hildenbrand <david@redhat.com> Acked-by: Pasha Tatashin <pasha.tatashin@soleen.com> Link: https://lore.kernel.org/r/20230515130958.32471-4-lrh2000@pku.edu.cn Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'mm/page_table_check.c')
0 files changed, 0 insertions, 0 deletions