Andreas Ziegler 030958c2d0 libbpf: Add NULL checks to bpf_object__{prev_map,next_map} ... [ Upstream commit cedc12c5b5 ] In the current state, an erroneous call to bpf_object__find_map_by_name(NULL, ...) leads to a segmentation fault through the following call chain: bpf_object__find_map_by_name(obj = NULL, ...) -> bpf_object__for_each_map(pos, obj = NULL) -> bpf_object__next_map((obj = NULL), NULL) -> return (obj = NULL)->maps While calling bpf_object__find_map_by_name with obj = NULL is obviously incorrect, this should not lead to a segmentation fault but rather be handled gracefully. As __bpf_map__iter already handles this situation correctly, we can delegate the check for the regular case there and only add a check in case the prev or next parameter is NULL. Signed-off-by: Andreas Ziegler <ziegler.andreas@siemens.com> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Link: https://lore.kernel.org/bpf/20240703083436.505124-1-ziegler.andreas@siemens.com Signed-off-by: Sasha Levin <sashal@kernel.org>		2024-09-12 11:11:36 +02:00
..
api	libapi: Add missing linux/types.h header to get the __u64 type on io.h	2024-01-25 15:35:51 -08:00
bpf	libbpf: Add NULL checks to bpf_object__{prev_map,next_map}	2024-09-12 11:11:36 +02:00
perf	perf evlist: Add perf_evlist__go_system_wide() helper	2024-06-12 11:13:02 +02:00
subcmd	libsubcmd: Fix parse-options memory leak	2024-06-12 11:12:30 +02:00
symbol
thermal
argv_split.c
bitmap.c
ctype.c
find_bit.c
hweight.c
list_sort.c
rbtree.c
slab.c
str_error_r.c
string.c
vsprintf.c
zalloc.c