| 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-2021-3752 | 2/16/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3744 | 3/4/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3743 | 3/4/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3739 | 3/7/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3736 | 8/23/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3732 | 3/7/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-37159 | 7/21/2021 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3715 | 3/2/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3679 | 8/5/2021 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3669 | 8/26/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3659 | 8/22/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3656 | 3/4/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3655 | 8/5/2021 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3653 | 9/29/2021 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3640 | 3/3/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3635 | 8/13/2021 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3612 | 7/9/2021 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3609 | 3/3/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | The Linux Kernel Organization | High | CVE-2021-3600 | 1/8/2024 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2021-3573 | 8/13/2021 |