Andreas Ziegler 532ee6e841 libbpf: Add NULL checks to bpf_object__{prev_map,next_map} ... [ Upstream commit cedc12c5b57f7efa6dbebfb2b140e8675f5a2616 ] 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-11-23 23:21:05 +01:00
..
api
bpf	libbpf: Add NULL checks to bpf_object__{prev_map,next_map}	2024-11-23 23:21:05 +01:00
lockdep
perf	libperf evlist: Avoid out-of-bounds access	2024-11-19 09:23:14 +01:00
subcmd	libsubcmd: Fix parse-options memory leak	2024-11-19 12:27:05 +01:00
symbol
traceevent
argv_split.c
bitmap.c
ctype.c
find_bit.c
hweight.c
rbtree.c
str_error_r.c
string.c
vsprintf.c
zalloc.c