| Version | |
|---|---|
| conf-linux-libc-dev.0 (latest) |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| kernel-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-6828 | 10/16/2016 |
| linux-api-headers | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-6791 | 1/12/2017 |
| kernel-headers | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-6791 | 1/12/2017 |
| linux-headers | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-6791 | 1/12/2017 |
| linux-libc-dev | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-6791 | 1/12/2017 |
| linux-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-6790 | 1/12/2017 |
| linux-libc-dev | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-6790 | 1/12/2017 |
| kernel-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-6790 | 1/12/2017 |
| linux-api-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-6790 | 1/12/2017 |
| linux-libc-dev | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-6789 | 1/12/2017 |
| linux-headers | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-6789 | 1/12/2017 |
| linux-api-headers | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-6789 | 1/12/2017 |
| kernel-headers | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-6789 | 1/12/2017 |
| kernel-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-6787 | 12/28/2016 |
| linux-libc-dev | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-6787 | 12/28/2016 |
| linux-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-6787 | 12/28/2016 |
| linux-api-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-6787 | 12/28/2016 |
| linux-api-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-6786 | 12/28/2016 |
| linux-libc-dev | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-6786 | 12/28/2016 |
| linux-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-6786 | 12/28/2016 |