| 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-2016-6327 | 10/16/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-6213 | 12/28/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-6198 | 8/6/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-6197 | 8/6/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-6187 | 8/6/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-6162 | 8/6/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-6156 | 8/6/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-6136 | 8/6/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-6130 | 7/3/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-5870 | 4/4/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-5856 | 4/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-5829 | 6/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-5828 | 6/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-5728 | 6/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-5696 | 8/6/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-5412 | 8/6/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-5400 | 8/6/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-5344 | 8/30/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-5343 | 10/10/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-5342 | 8/30/2016 |