seccomp: kill process instead of thread for unknown actions
authorRich Felker <dalias@libc.org>
Sat, 29 Aug 2020 01:56:13 +0000 (21:56 -0400)
committerKees Cook <keescook@chromium.org>
Tue, 8 Sep 2020 19:00:49 +0000 (12:00 -0700)
commit4d671d922d51907bc41f1f7f2dc737c928ae78fd
treedb573e5373b66886a76ffb82e1254808d3a12e2b
parente839317900e9f13c83d8711d684de88c625b307a
seccomp: kill process instead of thread for unknown actions

Asynchronous termination of a thread outside of the userspace thread
library's knowledge is an unsafe operation that leaves the process in
an inconsistent, corrupt, and possibly unrecoverable state. In order
to make new actions that may be added in the future safe on kernels
not aware of them, change the default action from
SECCOMP_RET_KILL_THREAD to SECCOMP_RET_KILL_PROCESS.

Signed-off-by: Rich Felker <dalias@libc.org>
Link: https://lore.kernel.org/r/20200829015609.GA32566@brightrain.aerifal.cx
[kees: Fixed up coredump selection logic to match]
Signed-off-by: Kees Cook <keescook@chromium.org>
kernel/seccomp.c