| Version | |
|---|---|
| hvsock.3.1.0 (latest) | |
| hvsock.3.0.1 | |
| hvsock.3.0.0 | |
| hvsock.2.0.0 | |
| hvsock.1.0.2 |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| kernel-headers | hvsock.3.1.0 | n/a | Unknown | CVE-2017-9211 | 5/23/2017 |
| linux-headers | hvsock.2.0.0 | n/a | Unknown | CVE-2017-9211 | 5/23/2017 |
| linux-libc-dev | hvsock.3.1.0 | n/a | Unknown | CVE-2017-9211 | 5/23/2017 |
| kernel-headers | hvsock.2.0.0 | n/a | Unknown | CVE-2017-9211 | 5/23/2017 |
| kernel-headers | hvsock.3.0.0 | n/a | Unknown | CVE-2017-9211 | 5/23/2017 |
| linux-libc-dev | hvsock.2.0.0 | n/a | Unknown | CVE-2017-9211 | 5/23/2017 |
| linux-headers | hvsock.3.1.0 | n/a | Unknown | CVE-2017-9211 | 5/23/2017 |
| linux-libc-dev | hvsock.3.0.0 | n/a | Unknown | CVE-2017-9211 | 5/23/2017 |
| linux-headers | hvsock.3.0.0 | n/a | Unknown | CVE-2017-9211 | 5/23/2017 |
| linux-headers | hvsock.2.0.0 | n/a | Unknown | CVE-2017-9150 | 5/22/2017 |
| kernel-headers | hvsock.3.1.0 | n/a | Unknown | CVE-2017-9150 | 5/22/2017 |
| kernel-headers | hvsock.3.0.0 | n/a | Unknown | CVE-2017-9150 | 5/22/2017 |
| kernel-headers | hvsock.2.0.0 | n/a | Unknown | CVE-2017-9150 | 5/22/2017 |
| linux-libc-dev | hvsock.3.1.0 | n/a | Unknown | CVE-2017-9150 | 5/22/2017 |
| linux-libc-dev | hvsock.2.0.0 | n/a | Unknown | CVE-2017-9150 | 5/22/2017 |
| linux-libc-dev | hvsock.3.0.0 | n/a | Unknown | CVE-2017-9150 | 5/22/2017 |
| linux-headers | hvsock.3.0.0 | n/a | Unknown | CVE-2017-9150 | 5/22/2017 |
| linux-headers | hvsock.3.1.0 | n/a | Unknown | CVE-2017-9150 | 5/22/2017 |
| kernel-headers | hvsock.3.1.0 | n/a | Unknown | CVE-2017-9077 | 5/19/2017 |
| linux-headers | hvsock.2.0.0 | n/a | Unknown | CVE-2017-9077 | 5/19/2017 |