Sargun Dhillon 771b894f2f samples/seccomp: Zero out members based on seccomp_notif_sizes ... The sizes by which seccomp_notif and seccomp_notif_resp are allocated are based on the SECCOMP_GET_NOTIF_SIZES ioctl. This allows for graceful extension of these datastructures. If userspace zeroes out the datastructure based on its version, and it is lagging behind the kernel's version, it will end up sending trailing garbage. On the other hand, if it is ahead of the kernel version, it will write extra zero space, and potentially cause corruption. Signed-off-by: Sargun Dhillon <sargun@sargun.me> Suggested-by: Tycho Andersen <tycho@tycho.ws> Link: https://lore.kernel.org/r/20191230203503.4925-1-sargun@sargun.me Fixes: fec7b66905 ("samples: add an example of seccomp user trap") Cc: stable@vger.kernel.org Signed-off-by: Kees Cook <keescook@chromium.org>		2020-01-02 13:03:39 -08:00
..
auxdisplay
binderfs
bpf
configfs
connector
ftrace
hidraw
hw_breakpoint
kdb
kfifo
kobject
kprobes
livepatch
mei
mic/mpssd
pidfd
pktgen
qmi
rpmsg
seccomp	samples/seccomp: Zero out members based on seccomp_notif_sizes	2020-01-02 13:03:39 -08:00
timers
trace_events
trace_printk
uhid
v4l
vfio-mdev
vfs
watchdog
Kconfig
Makefile