libbpf: Prevent null-pointer dereference when prog to load has no BTF
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.8.126.9.36.10In the Linux kernel, the following vulnerability has been resolved:
libbpf: Prevent null-pointer dereference when prog to load has no BTF
In bpf_objec_load_prog(), there's no guarantee that obj->btf is non-NULL when passing it to btf__fd(), and this function does not perform any check before dereferencing its argument (as bpf_object__btf_fd() used to do). As a consequence, we get segmentation fault errors in bpftool (for example) when trying to load programs that come without BTF information.
v2: Keep btf__fd() in the fix instead of reverting to bpf_object__btf_fd().
From the CVE record · Linux
In the Linux kernel's libbpf, loading a BPF program without BTF information can dereference a null pointer. This can cause a segmentation fault in tools such as bpftool; the input does not specify an attacker scenario, authentication requirements, or network exposure.
Engineers running Linux kernel versions that include the affected libbpf code should check their installations; affected versions are not specified.