| 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-44033 | 10/30/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Medium | CVE-2022-44032 | 10/30/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | linux | High | CVE-2022-43945 | 11/4/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-4379 | 1/10/2023 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-4378 | 1/5/2023 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Medium | CVE-2022-43750 | 10/26/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux | High | CVE-2022-42896 - Info Leak in l2cap_core in the Linux Kernel | 11/23/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-42722 | 10/13/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Medium | CVE-2022-42721 | 10/13/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-42720 | 10/13/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-42719 | 10/13/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-42703 | 10/9/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Medium | CVE-2022-4269 | 12/5/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux | Medium | CVE-2022-42432 | 3/29/2023 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux | Medium | CVE-2022-42329 | 12/7/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux | Medium | CVE-2022-42328 | 12/7/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2022-41858 | 1/17/2023 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-41850 | 9/30/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2022-41849 | 9/30/2022 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Medium | CVE-2022-41848 | 9/30/2022 |