| 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-headers | hvsock.3.1.0 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| kernel-headers | hvsock.3.0.0 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-libc-dev | hvsock.2.0.0 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-libc-dev | hvsock.3.1.0 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| kernel-headers | hvsock.2.0.0 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-libc-dev | hvsock.3.0.0 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-libc-dev | hvsock.3.1.0 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | hvsock.3.1.0 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-libc-dev | hvsock.2.0.0 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| kernel-headers | hvsock.3.1.0 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | hvsock.2.0.0 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-libc-dev | hvsock.3.0.0 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | hvsock.3.0.0 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| kernel-headers | hvsock.3.0.0 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| kernel-headers | hvsock.2.0.0 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-libc-dev | hvsock.3.1.0 | Linux Foundation | Unknown | CVE-2018-5814 | 6/12/2018 |
| kernel-headers | hvsock.2.0.0 | Linux Foundation | Unknown | CVE-2018-5814 | 6/12/2018 |
| linux-headers | hvsock.3.0.0 | Linux Foundation | Unknown | CVE-2018-5814 | 6/12/2018 |
| linux-headers | hvsock.3.1.0 | Linux Foundation | Unknown | CVE-2018-5814 | 6/12/2018 |
| kernel-headers | hvsock.3.1.0 | Linux Foundation | Unknown | CVE-2018-5814 | 6/12/2018 |