bpf: Sanitize BTF data pointer after module is loaded
authorAndrii Nakryiko <andrii@kernel.org>
Sat, 21 Nov 2020 07:08:29 +0000 (23:08 -0800)
committerDaniel Borkmann <daniel@iogearbox.net>
Tue, 24 Nov 2020 23:05:21 +0000 (00:05 +0100)
Given .BTF section is not allocatable, it will get trimmed after module is
loaded. BPF system handles that properly by creating an independent copy of
data. But prevent any accidental misused by resetting the pointer to BTF data.

Fixes: 36e68442d1af ("bpf: Load and verify kernel module BTFs")
Suggested-by: Jessica Yu <jeyu@kernel.org>
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Acked-by: Jessica Yu <jeyu@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Link: https://lore.kernel.org/bpf/20201121070829.2612884-2-andrii@kernel.org
kernel/module.c

index f2996b02ab2e498bda721159fa4bc6063924cf4e..18f259d61d1473471ef111698b2946cd6d74a52f 100644 (file)
@@ -3709,6 +3709,11 @@ static noinline int do_init_module(struct module *mod)
        mod->init_layout.ro_size = 0;
        mod->init_layout.ro_after_init_size = 0;
        mod->init_layout.text_size = 0;
+#ifdef CONFIG_DEBUG_INFO_BTF_MODULES
+       /* .BTF is not SHF_ALLOC and will get removed, so sanitize pointer */
+       mod->btf_data = NULL;
+       mod->btf_data_size = 0;
+#endif
        /*
         * We want to free module_init, but be aware that kallsyms may be
         * walking this with preempt disabled.  In all the failure paths, we