| 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 |
|---|---|---|---|---|---|
| linux-libc-dev | hvsock.2.0.0 | n/a | Unknown | CVE-2017-16995 | 12/22/2017 |
| linux-headers | hvsock.3.1.0 | n/a | Unknown | CVE-2017-16995 | 12/22/2017 |
| linux-headers | hvsock.3.1.0 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| linux-libc-dev | hvsock.3.0.0 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| kernel-headers | hvsock.3.0.0 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| kernel-headers | hvsock.2.0.0 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| linux-headers | hvsock.3.0.0 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| linux-headers | hvsock.2.0.0 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| kernel-headers | hvsock.3.1.0 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| linux-libc-dev | hvsock.2.0.0 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| linux-libc-dev | hvsock.3.1.0 | n/a | Unknown | CVE-2017-16994 | 11/27/2017 |
| linux-headers | hvsock.3.0.0 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |
| linux-libc-dev | hvsock.3.0.0 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |
| kernel-headers | hvsock.3.0.0 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |
| kernel-headers | hvsock.2.0.0 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |
| kernel-headers | hvsock.3.1.0 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |
| linux-headers | hvsock.2.0.0 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |
| linux-libc-dev | hvsock.3.1.0 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |
| linux-headers | hvsock.3.1.0 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |
| linux-libc-dev | hvsock.2.0.0 | n/a | Unknown | CVE-2017-16939 | 11/24/2017 |