| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| linux-headers | solo5-bindings-spt.0.6.6 | Google Inc. | Unknown | CVE-2016-8425 | 1/12/2017 |
| linux-headers | solo5-bindings-spt.0.6.5 | Google Inc. | Unknown | CVE-2016-8425 | 1/12/2017 |
| kernel-headers | solo5-bindings-spt.0.6.4 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| kernel-headers | solo5-bindings-spt.0.6.2 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| kernel-headers | solo5-bindings-spt.0.6.7 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| linux-libc-dev | solo5-bindings-spt.0.6.8 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| linux-libc-dev | solo5-bindings-spt.0.6.7 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| linux-libc-dev | solo5-bindings-spt.0.6.6 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| kernel-headers | solo5-bindings-spt.0.6.6 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| kernel-headers | solo5-bindings-spt.0.6.5 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| linux-headers | solo5-bindings-spt.0.6.4 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| linux-headers | solo5-bindings-spt.0.6.8 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| kernel-headers | solo5-bindings-spt.0.6.8 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| linux-libc-dev | solo5-bindings-spt.0.6.2 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| linux-headers | solo5-bindings-spt.0.6.5 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| kernel-headers | solo5-bindings-spt.0.6.9 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| linux-libc-dev | solo5-bindings-spt.0.6.9 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| linux-headers | solo5-bindings-spt.0.6.7 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| kernel-headers | solo5-bindings-spt.0.6.3 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |
| linux-libc-dev | solo5-bindings-spt.0.6.4 | n/a | Unknown | CVE-2016-8424 | 1/12/2017 |