| 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-2977 | 9/14/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-2964 | 9/9/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-2961 | 8/29/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-2959 | 8/25/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-29582 | 4/22/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux | High | CVE-2022-29581 | 5/17/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-2938 | 8/23/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-29156 | 4/13/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-2905 | 9/9/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-28893 | 4/11/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-28796 | 4/8/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-2873 | 8/22/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-28390 | 4/3/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-28389 | 4/3/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Medium | CVE-2022-28388 | 4/3/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Medium | CVE-2022-28356 | 4/2/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-27950 | 3/28/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux Kernel | Medium | CVE-2022-2785 - Arbitrary Memory read in BPF Linux Kernel | 9/23/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-27666 | 3/23/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-27223 | 3/15/2022 |