| Version | |
|---|---|
| conf-linux-libc-dev.0 (latest) |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| linux-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-5244 | 6/27/2016 |
| kernel-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-5243 | 6/27/2016 |
| linux-libc-dev | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-5243 | 6/27/2016 |
| linux-api-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-5243 | 6/27/2016 |
| linux-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-5243 | 6/27/2016 |
| linux-api-headers | conf-linux-libc-dev.0 | n/a | High | CVE-2016-5195 | 11/10/2016 |
| linux-libc-dev | conf-linux-libc-dev.0 | n/a | High | CVE-2016-5195 | 11/10/2016 |
| linux-headers | conf-linux-libc-dev.0 | n/a | High | CVE-2016-5195 | 11/10/2016 |
| kernel-headers | conf-linux-libc-dev.0 | n/a | High | CVE-2016-5195 | 11/10/2016 |
| kernel-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-4998 | 7/3/2016 |
| linux-api-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-4998 | 7/3/2016 |
| linux-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-4998 | 7/3/2016 |
| linux-libc-dev | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-4998 | 7/3/2016 |
| linux-libc-dev | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-4997 | 7/3/2016 |
| kernel-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-4997 | 7/3/2016 |
| linux-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-4997 | 7/3/2016 |
| linux-api-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-4997 | 7/3/2016 |
| kernel-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-4951 | 5/23/2016 |
| linux-libc-dev | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-4951 | 5/23/2016 |
| linux-api-headers | conf-linux-libc-dev.0 | n/a | Unknown | CVE-2016-4951 | 5/23/2016 |