| 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-48502 | 5/31/2023 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-48425 | 3/19/2023 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-48424 | 3/19/2023 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-48423 | 3/19/2023 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Medium | CVE-2022-4842 | 1/12/2023 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Medium | CVE-2022-47946 | 12/23/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-47943 | 12/23/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-47942 | 12/23/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-47941 | 12/23/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-47940 | 12/23/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Critical | CVE-2022-47939 | 12/23/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Medium | CVE-2022-47938 | 12/23/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Medium | CVE-2022-47929 | 1/17/2023 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-47521 | 12/18/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-47520 | 12/18/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-47519 | 12/18/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-47518 | 12/18/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-4744 | 3/30/2023 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux | High | CVE-2022-4696 | 1/11/2023 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Medium | CVE-2022-4662 | 12/22/2022 |