| 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 | [UNKNOWN] | Medium | CVE-2018-10883 | 7/30/2018 |
| linux-headers | hvsock.3.0.0 | [UNKNOWN] | Medium | CVE-2018-10883 | 7/30/2018 |
| linux-headers | hvsock.2.0.0 | [UNKNOWN] | Medium | CVE-2018-10883 | 7/30/2018 |
| linux-libc-dev | hvsock.2.0.0 | [UNKNOWN] | Medium | CVE-2018-10883 | 7/30/2018 |
| linux-libc-dev | hvsock.3.1.0 | [UNKNOWN] | Medium | CVE-2018-10883 | 7/30/2018 |
| linux-libc-dev | hvsock.3.0.0 | [UNKNOWN] | Medium | CVE-2018-10883 | 7/30/2018 |
| kernel-headers | hvsock.2.0.0 | [UNKNOWN] | Medium | CVE-2018-10883 | 7/30/2018 |
| kernel-headers | hvsock.3.1.0 | [UNKNOWN] | Medium | CVE-2018-10883 | 7/30/2018 |
| linux-headers | hvsock.2.0.0 | [UNKNOWN] | Medium | CVE-2018-10881 | 7/26/2018 |
| kernel-headers | hvsock.2.0.0 | [UNKNOWN] | Medium | CVE-2018-10881 | 7/26/2018 |
| kernel-headers | hvsock.3.1.0 | [UNKNOWN] | Medium | CVE-2018-10881 | 7/26/2018 |
| kernel-headers | hvsock.3.0.0 | [UNKNOWN] | Medium | CVE-2018-10881 | 7/26/2018 |
| linux-libc-dev | hvsock.3.0.0 | [UNKNOWN] | Medium | CVE-2018-10881 | 7/26/2018 |
| linux-headers | hvsock.3.0.0 | [UNKNOWN] | Medium | CVE-2018-10881 | 7/26/2018 |
| linux-libc-dev | hvsock.3.1.0 | [UNKNOWN] | Medium | CVE-2018-10881 | 7/26/2018 |
| linux-libc-dev | hvsock.2.0.0 | [UNKNOWN] | Medium | CVE-2018-10881 | 7/26/2018 |
| linux-headers | hvsock.3.1.0 | [UNKNOWN] | Medium | CVE-2018-10881 | 7/26/2018 |
| linux-headers | hvsock.3.0.0 | [UNKNOWN] | Medium | CVE-2018-10880 | 7/25/2018 |
| linux-headers | hvsock.3.1.0 | [UNKNOWN] | Medium | CVE-2018-10880 | 7/25/2018 |
| kernel-headers | hvsock.3.1.0 | [UNKNOWN] | Medium | CVE-2018-10880 | 7/25/2018 |