diff options
author | Kuan-Wei Chiu <visitorckw@gmail.com> | 2024-09-10 18:02:07 +0300 |
---|---|---|
committer | Andrii Nakryiko <andrii@kernel.org> | 2024-09-10 21:40:55 +0300 |
commit | f04e2ad394e2755d0bb2d858ecb5598718bf00d5 (patch) | |
tree | 78381e718fea8b5ec2318d612a6feb434c1ae4b6 /kernel/bpf/arraymap.c | |
parent | 8c8b4759740359a6f2e7ffdf6531dea871130c63 (diff) | |
download | linux-f04e2ad394e2755d0bb2d858ecb5598718bf00d5.tar.xz |
bpftool: Fix undefined behavior in qsort(NULL, 0, ...)
When netfilter has no entry to display, qsort is called with
qsort(NULL, 0, ...). This results in undefined behavior, as UBSan
reports:
net.c:827:2: runtime error: null pointer passed as argument 1, which is declared to never be null
Although the C standard does not explicitly state whether calling qsort
with a NULL pointer when the size is 0 constitutes undefined behavior,
Section 7.1.4 of the C standard (Use of library functions) mentions:
"Each of the following statements applies unless explicitly stated
otherwise in the detailed descriptions that follow: If an argument to a
function has an invalid value (such as a value outside the domain of
the function, or a pointer outside the address space of the program, or
a null pointer, or a pointer to non-modifiable storage when the
corresponding parameter is not const-qualified) or a type (after
promotion) not expected by a function with variable number of
arguments, the behavior is undefined."
To avoid this, add an early return when nf_link_info is NULL to prevent
calling qsort with a NULL pointer.
Signed-off-by: Kuan-Wei Chiu <visitorckw@gmail.com>
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
Reviewed-by: Quentin Monnet <qmo@kernel.org>
Link: https://lore.kernel.org/bpf/20240910150207.3179306-1-visitorckw@gmail.com
Diffstat (limited to 'kernel/bpf/arraymap.c')
0 files changed, 0 insertions, 0 deletions