| Version | |
|---|---|
| conf-libbpf.0.1.0 (latest) |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Low | CVE-2022-33981 | 6/18/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux | Unknown | CVE-2022-33744 | 7/5/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux | Unknown | CVE-2022-33743 | 7/5/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux | Unknown | CVE-2022-33742 | 7/5/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | Xen | Unknown | CVE-2022-33742 | 7/5/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux | Unknown | CVE-2022-33741 | 7/5/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | Xen | Unknown | CVE-2022-33741 | 7/5/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux | Unknown | CVE-2022-33740 | 7/5/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | Xen | Unknown | CVE-2022-33740 | 7/5/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Medium | CVE-2022-3344 | 10/24/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Medium | CVE-2022-3303 | 9/27/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-32981 | 6/10/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-3239 | 9/19/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-3238 | 11/14/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-32296 | 6/5/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-32250 | 6/2/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-3202 | 9/14/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux | High | CVE-2022-3176 - Use-after-free in io_uring in Linux Kernel | 9/16/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-3170 | 9/13/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-3169 | 9/9/2022 |