| Version | |
|---|---|
| conf-linux-libc-dev.0 (latest) |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| kernel-headers | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-8392 | 1/12/2017 |
| linux-libc-dev | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-8391 | 1/12/2017 |
| kernel-headers | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-8391 | 1/12/2017 |
| linux-headers | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-8391 | 1/12/2017 |
| linux-api-headers | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-8391 | 1/12/2017 |
| linux-api-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-7917 | 11/16/2016 |
| kernel-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-7917 | 11/16/2016 |
| linux-libc-dev | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-7917 | 11/16/2016 |
| linux-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-7917 | 11/16/2016 |
| linux-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-7916 | 11/16/2016 |
| kernel-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-7916 | 11/16/2016 |
| linux-api-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-7916 | 11/16/2016 |
| linux-libc-dev | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-7916 | 11/16/2016 |
| linux-api-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-7915 | 11/16/2016 |
| kernel-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-7915 | 11/16/2016 |
| linux-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-7915 | 11/16/2016 |
| linux-libc-dev | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-7915 | 11/16/2016 |
| linux-libc-dev | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-7914 | 11/16/2016 |
| linux-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-7914 | 11/16/2016 |
| linux-api-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-7914 | 11/16/2016 |