| 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.0.0 | Linux | Medium | CVE-2022-3594 - Linux Kernel BPF r8152.c intr_callback logging of excessive data | 10/18/2022 |
| linux-libc-dev | hvsock.2.0.0 | Linux | Medium | CVE-2022-3594 - Linux Kernel BPF r8152.c intr_callback logging of excessive data | 10/18/2022 |
| linux-headers | hvsock.3.1.0 | Linux | Medium | CVE-2022-3594 - Linux Kernel BPF r8152.c intr_callback logging of excessive data | 10/18/2022 |
| linux-libc-dev | hvsock.3.0.0 | n/a | Medium | CVE-2022-3586 | 10/19/2022 |
| linux-headers | hvsock.2.0.0 | n/a | Medium | CVE-2022-3586 | 10/19/2022 |
| linux-headers | hvsock.3.1.0 | n/a | Medium | CVE-2022-3586 | 10/19/2022 |
| linux-headers | hvsock.3.0.0 | n/a | Medium | CVE-2022-3586 | 10/19/2022 |
| kernel-headers | hvsock.2.0.0 | n/a | Medium | CVE-2022-3586 | 10/19/2022 |
| linux-libc-dev | hvsock.2.0.0 | n/a | Medium | CVE-2022-3586 | 10/19/2022 |
| kernel-headers | hvsock.3.0.0 | n/a | Medium | CVE-2022-3586 | 10/19/2022 |
| kernel-headers | hvsock.3.1.0 | n/a | Medium | CVE-2022-3586 | 10/19/2022 |
| linux-libc-dev | hvsock.3.1.0 | n/a | Medium | CVE-2022-3586 | 10/19/2022 |
| linux-headers | hvsock.3.1.0 | n/a | High | CVE-2022-3577 | 10/20/2022 |
| kernel-headers | hvsock.3.1.0 | n/a | High | CVE-2022-3577 | 10/20/2022 |
| linux-libc-dev | hvsock.3.0.0 | n/a | High | CVE-2022-3577 | 10/20/2022 |
| linux-headers | hvsock.3.0.0 | n/a | High | CVE-2022-3577 | 10/20/2022 |
| kernel-headers | hvsock.3.0.0 | n/a | High | CVE-2022-3577 | 10/20/2022 |
| kernel-headers | hvsock.2.0.0 | n/a | High | CVE-2022-3577 | 10/20/2022 |
| linux-libc-dev | hvsock.2.0.0 | n/a | High | CVE-2022-3577 | 10/20/2022 |
| linux-libc-dev | hvsock.3.1.0 | n/a | High | CVE-2022-3577 | 10/20/2022 |