| Version | |
|---|---|
| conf-libbpf.0.1.0 (latest) |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0812 | 8/29/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux | Critical | CVE-2022-0742 - Memory leak in ICMP6 in Linux Kernel | 3/18/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0646 | 2/18/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0617 | 2/16/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0516 | 3/8/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0500 | 3/25/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0494 | 3/25/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0492 | 3/3/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0487 | 2/4/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0480 | 8/29/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0435 | 3/25/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0433 | 3/9/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0382 | 2/11/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0330 | 3/25/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0322 | 3/25/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0264 | 2/4/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-0185 | 2/11/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0171 | 8/26/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-0168 | 8/26/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux | Low | CVE-2021-47671 - can: etas_es58x: es58x_rx_err_msg(): fix memory leak in error path | 4/17/2025 |