| 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 | Google Inc. | Unknown | CVE-2017-0569 | 4/7/2017 |
| kernel-headers | hvsock.2.0.0 | Google Inc. | Unknown | CVE-2017-0569 | 4/7/2017 |
| kernel-headers | hvsock.3.0.0 | Google Inc. | Unknown | CVE-2017-0569 | 4/7/2017 |
| linux-libc-dev | hvsock.2.0.0 | Google Inc. | Unknown | CVE-2017-0569 | 4/7/2017 |
| linux-headers | hvsock.3.1.0 | Google Inc. | Unknown | CVE-2017-0569 | 4/7/2017 |
| linux-libc-dev | hvsock.3.0.0 | Google Inc. | Unknown | CVE-2017-0569 | 4/7/2017 |
| linux-headers | hvsock.2.0.0 | Google Inc. | Unknown | CVE-2017-0569 | 4/7/2017 |
| linux-headers | hvsock.3.0.0 | Google Inc. | Unknown | CVE-2017-0569 | 4/7/2017 |
| kernel-headers | hvsock.3.0.0 | Google Inc. | Unknown | CVE-2017-0568 | 4/7/2017 |
| linux-libc-dev | hvsock.2.0.0 | Google Inc. | Unknown | CVE-2017-0568 | 4/7/2017 |
| linux-headers | hvsock.2.0.0 | Google Inc. | Unknown | CVE-2017-0568 | 4/7/2017 |
| linux-headers | hvsock.3.0.0 | Google Inc. | Unknown | CVE-2017-0568 | 4/7/2017 |
| kernel-headers | hvsock.2.0.0 | Google Inc. | Unknown | CVE-2017-0568 | 4/7/2017 |
| kernel-headers | hvsock.3.1.0 | Google Inc. | Unknown | CVE-2017-0568 | 4/7/2017 |
| linux-headers | hvsock.3.1.0 | Google Inc. | Unknown | CVE-2017-0568 | 4/7/2017 |
| linux-libc-dev | hvsock.3.1.0 | Google Inc. | Unknown | CVE-2017-0568 | 4/7/2017 |
| linux-libc-dev | hvsock.3.0.0 | Google Inc. | Unknown | CVE-2017-0568 | 4/7/2017 |
| linux-headers | hvsock.3.0.0 | Google Inc. | Unknown | CVE-2017-0567 | 4/7/2017 |
| linux-headers | hvsock.3.1.0 | Google Inc. | Unknown | CVE-2017-0567 | 4/7/2017 |
| linux-libc-dev | hvsock.3.0.0 | Google Inc. | Unknown | CVE-2017-0567 | 4/7/2017 |