Files
kernel/include/linux
Yonghong Song c6f1bfe89a bpf: reject program if a __user tagged memory accessed in kernel way
BPF verifier supports direct memory access for BPF_PROG_TYPE_TRACING type
of bpf programs, e.g., a->b. If "a" is a pointer
pointing to kernel memory, bpf verifier will allow user to write
code in C like a->b and the verifier will translate it to a kernel
load properly. If "a" is a pointer to user memory, it is expected
that bpf developer should be bpf_probe_read_user() helper to
get the value a->b. Without utilizing BTF __user tagging information,
current verifier will assume that a->b is a kernel memory access
and this may generate incorrect result.

Now BTF contains __user information, it can check whether the
pointer points to a user memory or not. If it is, the verifier
can reject the program and force users to use bpf_probe_read_user()
helper explicitly.

In the future, we can easily extend btf_add_space for other
address space tagging, for example, rcu/percpu etc.

Signed-off-by: Yonghong Song <yhs@fb.com>
Link: https://lore.kernel.org/r/20220127154606.654961-1-yhs@fb.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
2022-01-27 12:03:46 -08:00
..
2022-01-09 10:36:51 -07:00
2021-12-10 17:10:55 -08:00
2021-12-10 12:51:28 +01:00
2021-12-15 15:58:40 +01:00
2022-01-20 08:52:54 +02:00
2022-01-04 13:15:33 -05:00
2021-12-17 09:06:15 +01:00
2021-12-20 09:03:05 +01:00
2022-01-15 20:37:06 +02:00
2021-12-16 22:22:20 +01:00
2022-01-12 10:14:09 -06:00
2022-01-15 16:30:28 +02:00
2022-01-15 16:30:28 +02:00
2022-01-08 12:43:57 -06:00
2022-01-26 21:17:53 -08:00
2021-12-30 12:13:04 +01:00
2022-01-14 18:50:52 -05:00
2021-12-09 10:49:56 -08:00
2022-01-08 00:28:41 -05:00