| 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-2847 | 4/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2782 | 4/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2550 | 4/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2549 | 4/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2548 | 4/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2547 | 4/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2546 | 4/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2545 | 4/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2544 | 4/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2543 | 4/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2384 | 4/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2383 | 4/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2188 | 5/2/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2187 | 5/2/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2186 | 5/2/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2185 | 5/2/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2184 | 4/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2143 | 4/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2117 | 5/2/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-2085 | 4/27/2016 |