| Version | |
|---|---|
| conf-libbpf.0.1.0 (latest) |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8399 | 1/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8398 | 1/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8397 | 1/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8395 | 1/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8394 | 1/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8393 | 1/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8392 | 1/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-8391 | 1/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-7917 | 11/16/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-7916 | 11/16/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-7915 | 11/16/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-7914 | 11/16/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-7913 | 11/16/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-7912 | 11/16/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-7911 | 11/16/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-7910 | 11/16/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-7425 | 10/16/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-7117 | 10/10/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-7097 | 10/16/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-7042 | 10/16/2016 |