| 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.0.0 | n/a | Unknown | CVE-2022-26878 | 3/11/2022 |
| kernel-headers | hvsock.3.1.0 | n/a | Unknown | CVE-2022-26878 | 3/11/2022 |
| kernel-headers | hvsock.2.0.0 | n/a | Unknown | CVE-2022-26878 | 3/11/2022 |
| linux-libc-dev | hvsock.3.0.0 | n/a | Unknown | CVE-2022-26878 | 3/11/2022 |
| linux-headers | hvsock.3.1.0 | n/a | Unknown | CVE-2022-26878 | 3/11/2022 |
| linux-headers | hvsock.2.0.0 | n/a | Unknown | CVE-2022-26878 | 3/11/2022 |
| linux-libc-dev | hvsock.3.1.0 | n/a | Unknown | CVE-2022-26878 | 3/11/2022 |
| linux-libc-dev | hvsock.2.0.0 | n/a | Unknown | CVE-2022-26490 | 3/6/2022 |
| linux-libc-dev | hvsock.3.1.0 | n/a | Unknown | CVE-2022-26490 | 3/6/2022 |
| linux-headers | hvsock.3.0.0 | n/a | Unknown | CVE-2022-26490 | 3/6/2022 |
| linux-headers | hvsock.3.1.0 | n/a | Unknown | CVE-2022-26490 | 3/6/2022 |
| kernel-headers | hvsock.2.0.0 | n/a | Unknown | CVE-2022-26490 | 3/6/2022 |
| linux-libc-dev | hvsock.3.0.0 | n/a | Unknown | CVE-2022-26490 | 3/6/2022 |
| linux-headers | hvsock.2.0.0 | n/a | Unknown | CVE-2022-26490 | 3/6/2022 |
| kernel-headers | hvsock.3.0.0 | n/a | Unknown | CVE-2022-26490 | 3/6/2022 |
| kernel-headers | hvsock.3.1.0 | n/a | Unknown | CVE-2022-26490 | 3/6/2022 |
| kernel-headers | hvsock.3.0.0 | n/a | Unknown | CVE-2022-2639 | 9/1/2022 |
| linux-libc-dev | hvsock.3.1.0 | n/a | Unknown | CVE-2022-2639 | 9/1/2022 |
| linux-libc-dev | hvsock.2.0.0 | n/a | Unknown | CVE-2022-2639 | 9/1/2022 |
| linux-headers | hvsock.3.1.0 | n/a | Unknown | CVE-2022-2639 | 9/1/2022 |