| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| linux-headers | xapi-stdext-unix.4.19.0 | n/a | Unknown | CVE-2016-5243 | 6/27/2016 |
| linux-headers | xapi-stdext-unix.4.16.0 | n/a | Unknown | CVE-2016-5243 | 6/27/2016 |
| linux-headers | xapi-stdext-unix.4.22.0 | n/a | Unknown | CVE-2016-5243 | 6/27/2016 |
| linux-headers | xapi-stdext-unix.4.24.0 | n/a | Unknown | CVE-2016-5243 | 6/27/2016 |
| linux-headers | xapi-stdext-unix.4.24.0 | n/a | High | CVE-2016-5195 | 11/10/2016 |
| linux-headers | xapi-stdext-unix.4.20.0 | n/a | High | CVE-2016-5195 | 11/10/2016 |
| linux-headers | xapi-stdext-unix.4.23.0 | n/a | High | CVE-2016-5195 | 11/10/2016 |
| linux-headers | xapi-stdext-unix.4.19.0 | n/a | High | CVE-2016-5195 | 11/10/2016 |
| linux-headers | xapi-stdext-unix.4.16.0 | n/a | High | CVE-2016-5195 | 11/10/2016 |
| linux-headers | xapi-stdext-unix.4.14.0 | n/a | High | CVE-2016-5195 | 11/10/2016 |
| linux-headers | xapi-stdext-unix.4.22.0 | n/a | High | CVE-2016-5195 | 11/10/2016 |
| linux-headers | xapi-stdext-unix.4.21.0 | n/a | High | CVE-2016-5195 | 11/10/2016 |
| linux-headers | xapi-stdext-unix.4.24.0 | n/a | Unknown | CVE-2016-4998 | 7/3/2016 |
| linux-headers | xapi-stdext-unix.4.14.0 | n/a | Unknown | CVE-2016-4998 | 7/3/2016 |
| linux-headers | xapi-stdext-unix.4.16.0 | n/a | Unknown | CVE-2016-4998 | 7/3/2016 |
| linux-headers | xapi-stdext-unix.4.21.0 | n/a | Unknown | CVE-2016-4998 | 7/3/2016 |
| linux-headers | xapi-stdext-unix.4.20.0 | n/a | Unknown | CVE-2016-4998 | 7/3/2016 |
| linux-headers | xapi-stdext-unix.4.22.0 | n/a | Unknown | CVE-2016-4998 | 7/3/2016 |
| linux-headers | xapi-stdext-unix.4.23.0 | n/a | Unknown | CVE-2016-4998 | 7/3/2016 |
| linux-headers | xapi-stdext-unix.4.19.0 | n/a | Unknown | CVE-2016-4998 | 7/3/2016 |