| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| linux-headers | xapi-stdext-unix.4.21.0 | Google Inc. | Unknown | CVE-2016-8391 | 1/12/2017 |
| linux-headers | xapi-stdext-unix.4.24.0 | Google Inc. | Unknown | CVE-2016-8391 | 1/12/2017 |
| linux-headers | xapi-stdext-unix.4.14.0 | Google Inc. | Unknown | CVE-2016-8391 | 1/12/2017 |
| linux-headers | xapi-stdext-unix.4.23.0 | Google Inc. | Unknown | CVE-2016-8391 | 1/12/2017 |
| linux-headers | xapi-stdext-unix.4.23.0 | n/a | Unknown | CVE-2016-7917 | 11/16/2016 |
| linux-headers | xapi-stdext-unix.4.24.0 | n/a | Unknown | CVE-2016-7917 | 11/16/2016 |
| linux-headers | xapi-stdext-unix.4.21.0 | n/a | Unknown | CVE-2016-7917 | 11/16/2016 |
| linux-headers | xapi-stdext-unix.4.19.0 | n/a | Unknown | CVE-2016-7917 | 11/16/2016 |
| linux-headers | xapi-stdext-unix.4.20.0 | n/a | Unknown | CVE-2016-7917 | 11/16/2016 |
| linux-headers | xapi-stdext-unix.4.22.0 | n/a | Unknown | CVE-2016-7917 | 11/16/2016 |
| linux-headers | xapi-stdext-unix.4.14.0 | n/a | Unknown | CVE-2016-7917 | 11/16/2016 |
| linux-headers | xapi-stdext-unix.4.16.0 | n/a | Unknown | CVE-2016-7917 | 11/16/2016 |
| linux-headers | xapi-stdext-unix.4.16.0 | n/a | Unknown | CVE-2016-7916 | 11/16/2016 |
| linux-headers | xapi-stdext-unix.4.23.0 | n/a | Unknown | CVE-2016-7916 | 11/16/2016 |
| linux-headers | xapi-stdext-unix.4.14.0 | n/a | Unknown | CVE-2016-7916 | 11/16/2016 |
| linux-headers | xapi-stdext-unix.4.19.0 | n/a | Unknown | CVE-2016-7916 | 11/16/2016 |
| linux-headers | xapi-stdext-unix.4.24.0 | n/a | Unknown | CVE-2016-7916 | 11/16/2016 |
| linux-headers | xapi-stdext-unix.4.21.0 | n/a | Unknown | CVE-2016-7916 | 11/16/2016 |
| linux-headers | xapi-stdext-unix.4.22.0 | n/a | Unknown | CVE-2016-7916 | 11/16/2016 |
| linux-headers | xapi-stdext-unix.4.20.0 | n/a | Unknown | CVE-2016-7916 | 11/16/2016 |