| Version | |
|---|---|
| vhd-format.0.9.1 (latest) | |
| vhd-format.0.13.0 | |
| vhd-format.0.12.3 | |
| vhd-format.0.12.2 | |
| vhd-format.0.12.1 | |
| vhd-format.0.12.0 |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| linux-headers | vhd-format.0.12.2 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | vhd-format.0.12.0 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | vhd-format.0.12.1 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | vhd-format.0.12.3 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | vhd-format.0.9.1 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | vhd-format.0.13.0 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | vhd-format.0.12.2 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | vhd-format.0.13.0 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | vhd-format.0.12.0 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | vhd-format.0.12.1 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | vhd-format.0.9.1 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | vhd-format.0.12.3 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | vhd-format.0.12.3 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | vhd-format.0.13.0 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | vhd-format.0.9.1 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | vhd-format.0.12.2 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | vhd-format.0.12.1 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | vhd-format.0.12.0 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | vhd-format.0.12.1 | Linux | Low | CVE-2022-3649 - Linux Kernel BPF inode.c nilfs_new_inode use after free | 10/21/2022 |
| linux-headers | vhd-format.0.9.1 | Linux | Low | CVE-2022-3649 - Linux Kernel BPF inode.c nilfs_new_inode use after free | 10/21/2022 |