| Version | |
|---|---|
| core.v0.17.1 (latest) | |
| core.v0.17.0 | |
| core.v0.16.2 | |
| core.v0.16.1 | |
| core.v0.16.0 | |
| core.v0.15.1 | |
| core.v0.15.0 | |
| core.v0.14.1 | |
| core.v0.14.0 | |
| core.v0.13.0 | |
| core.v0.12.4 | |
| core.v0.12.3 | |
| core.v0.12.2 |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| linux-headers | core.v0.12.2 | Google Inc. | Unknown | CVE-2016-8465 | 1/12/2017 |
| linux-headers | core.v0.12.3 | Google Inc. | Unknown | CVE-2016-8465 | 1/12/2017 |
| linux-headers | core.v0.13.0 | Google Inc. | Unknown | CVE-2016-8465 | 1/12/2017 |
| linux-headers | core.v0.12.4 | Google Inc. | Unknown | CVE-2016-8465 | 1/12/2017 |
| linux-headers | core.v0.12.3 | Google Inc. | Unknown | CVE-2016-8464 | 1/12/2017 |
| linux-headers | core.v0.12.4 | Google Inc. | Unknown | CVE-2016-8464 | 1/12/2017 |
| linux-headers | core.v0.14.0 | Google Inc. | Unknown | CVE-2016-8464 | 1/12/2017 |
| linux-headers | core.v0.12.2 | Google Inc. | Unknown | CVE-2016-8464 | 1/12/2017 |
| linux-headers | core.v0.13.0 | Google Inc. | Unknown | CVE-2016-8464 | 1/12/2017 |
| linux-headers | core.v0.14.1 | Google Inc. | Unknown | CVE-2016-8464 | 1/12/2017 |
| linux-headers | core.v0.14.1 | Google Inc. | Unknown | CVE-2016-8463 | 1/12/2017 |
| linux-headers | core.v0.12.4 | Google Inc. | Unknown | CVE-2016-8463 | 1/12/2017 |
| linux-headers | core.v0.12.2 | Google Inc. | Unknown | CVE-2016-8463 | 1/12/2017 |
| linux-headers | core.v0.12.3 | Google Inc. | Unknown | CVE-2016-8463 | 1/12/2017 |
| linux-headers | core.v0.13.0 | Google Inc. | Unknown | CVE-2016-8463 | 1/12/2017 |
| linux-headers | core.v0.14.0 | Google Inc. | Unknown | CVE-2016-8463 | 1/12/2017 |
| linux-headers | core.v0.14.0 | n/a | Unknown | CVE-2016-8461 | 1/12/2017 |
| linux-headers | core.v0.13.0 | n/a | Unknown | CVE-2016-8461 | 1/12/2017 |
| linux-headers | core.v0.14.1 | n/a | Unknown | CVE-2016-8461 | 1/12/2017 |
| linux-headers | core.v0.12.3 | n/a | Unknown | CVE-2016-8461 | 1/12/2017 |