| Version | |
|---|---|
| conf-linux-libc-dev.0 (latest) |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| linux-headers | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-10283 | 5/12/2017 |
| linux-headers | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-10277 | 5/12/2017 |
| linux-libc-dev | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-10277 | 5/12/2017 |
| kernel-headers | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-10277 | 5/12/2017 |
| linux-api-headers | conf-linux-libc-dev.0 | Google Inc. | Unknown | CVE-2016-10277 | 5/12/2017 |
| linux-libc-dev | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-10229 | 4/4/2017 |
| linux-api-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-10229 | 4/4/2017 |
| kernel-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-10229 | 4/4/2017 |
| linux-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-10229 | 4/4/2017 |
| linux-api-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-10208 | 2/6/2017 |
| kernel-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-10208 | 2/6/2017 |
| linux-libc-dev | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-10208 | 2/6/2017 |
| linux-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-10208 | 2/6/2017 |
| linux-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-10200 | 3/7/2017 |
| linux-libc-dev | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-10200 | 3/7/2017 |
| kernel-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-10200 | 3/7/2017 |
| linux-api-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-10200 | 3/7/2017 |
| kernel-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-10154 | 2/6/2017 |
| linux-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-10154 | 2/6/2017 |
| linux-api-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-10154 | 2/6/2017 |