| 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-8666 | 10/16/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-8660 | 10/16/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-8658 | 10/16/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-8655 | 12/8/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-8650 | 11/28/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-8646 | 11/28/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-8645 | 11/28/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-8636 | 2/22/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-8633 | 11/28/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-8632 | 11/28/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-8630 | 11/28/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8483 | 3/8/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8481 | 2/8/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8480 | 2/8/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8479 | 3/8/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8478 | 3/8/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8477 | 3/8/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8476 | 2/8/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8475 | 1/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8474 | 1/12/2017 |