[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241113191602.3541870-1-jeffxu@google.com>
Date: Wed, 13 Nov 2024 19:16:01 +0000
From: jeffxu@...omium.org
To: akpm@...ux-foundation.org,
keescook@...omium.org,
jannh@...gle.com,
torvalds@...ux-foundation.org,
adhemerval.zanella@...aro.org,
oleg@...hat.com
Cc: linux-kernel@...r.kernel.org,
linux-hardening@...r.kernel.org,
linux-mm@...ck.org,
jorgelo@...omium.org,
sroettger@...gle.com,
ojeda@...nel.org,
adobriyan@...il.com,
anna-maria@...utronix.de,
mark.rutland@....com,
linus.walleij@...aro.org,
Jason@...c4.com,
deller@....de,
rdunlap@...radead.org,
davem@...emloft.net,
hch@....de,
peterx@...hat.com,
hca@...ux.ibm.com,
f.fainelli@...il.com,
gerg@...nel.org,
dave.hansen@...ux.intel.com,
mingo@...nel.org,
ardb@...nel.org,
Liam.Howlett@...cle.com,
mhocko@...e.com,
42.hyeyoo@...il.com,
peterz@...radead.org,
ardb@...gle.com,
enh@...gle.com,
rientjes@...gle.com,
groeck@...omium.org,
lorenzo.stoakes@...cle.com,
Jeff Xu <jeffxu@...omium.org>
Subject: [PATCH v3 0/1] seal system mappings
From: Jeff Xu <jeffxu@...omium.org>
Seal vdso, vvar, sigpage, uprobes and vsyscall.
Those mappings are readonly or executable only, sealing can protect
them from ever changing or unmapped during the life time of the process.
For complete descriptions of memory sealing, please see mseal.rst [1].
System mappings such as vdso, vvar, and sigpage (for arm) are
generated by the kernel during program initialization, and are
sealed after creation.
Unlike the aforementioned mappings, the uprobe mapping is not
established during program startup. However, its lifetime is the same
as the process's lifetime [1]. It is sealed from creation.
The vdso, vvar, sigpage, and uprobe mappings all invoke the
_install_special_mapping() function. As no other mappings utilize this
function, it is logical to incorporate sealing logic within
_install_special_mapping(). This approach avoids the necessity of
modifying code across various architecture-specific implementations.
The vsyscall mapping, which has its own initialization function, is
sealed in the XONLY case, it seems to be the most common and secure
case of using vsyscall.
It is important to note that the CHECKPOINT_RESTORE feature (CRIU) may
alter the mapping of vdso, vvar, and sigpage during restore
operations. Consequently, this feature cannot be universally enabled
across all systems. To address this, a kernel configuration option has
been introduced to enable or disable this functionality.
[1] Documentation/userspace-api/mseal.rst
[2] https://lore.kernel.org/all/CABi2SkU9BRUnqf70-nksuMCQ+yyiWjo3fM4XkRkL-NrCZxYAyg@mail.gmail.com/
History:
V3:
Revert uprobe to v1 logic (Oleg Nesterov)
use CONFIG_SEAL_SYSTEM_MAPPINGS instead of _ALWAYS/_NEVER (Kees Cook)
Move kernel cmd line from fs/exec.c to mm/mseal.c and misc. refactor (Liam R. Howlett)
V2:
https://lore.kernel.org/all/20241014215022.68530-1-jeffxu@google.com/
Seal uprobe always (Oleg Nesterov)
Update comments and description (Randy Dunlap, Liam R.Howlett, Oleg Nesterov)
Rebase to linux_main
V1:
https://lore.kernel.org/all/20241004163155.3493183-1-jeffxu@google.com/
Jeff Xu (1):
exec: seal system mappings
.../admin-guide/kernel-parameters.txt | 10 +++++
arch/x86/entry/vsyscall/vsyscall_64.c | 9 ++++-
include/linux/mm.h | 12 ++++++
mm/mmap.c | 10 +++++
mm/mseal.c | 39 +++++++++++++++++++
security/Kconfig | 11 ++++++
6 files changed, 89 insertions(+), 2 deletions(-)
--
2.47.0.277.g8800431eea-goog
Powered by blists - more mailing lists