| 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.1 | n/a | Unknown | CVE-2018-6412 | 1/31/2018 |
| linux-headers | vhd-format.0.12.2 | n/a | Unknown | CVE-2018-6412 | 1/31/2018 |
| linux-headers | vhd-format.0.12.2 | n/a | Unknown | CVE-2018-5995 | 8/7/2018 |
| linux-headers | vhd-format.0.13.0 | n/a | Unknown | CVE-2018-5995 | 8/7/2018 |
| linux-headers | vhd-format.0.12.0 | n/a | Unknown | CVE-2018-5995 | 8/7/2018 |
| linux-headers | vhd-format.0.12.1 | n/a | Unknown | CVE-2018-5995 | 8/7/2018 |
| linux-headers | vhd-format.0.12.3 | n/a | Unknown | CVE-2018-5995 | 8/7/2018 |
| linux-headers | vhd-format.0.9.1 | n/a | Unknown | CVE-2018-5995 | 8/7/2018 |
| linux-headers | vhd-format.0.13.0 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-headers | vhd-format.0.12.1 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-headers | vhd-format.0.12.0 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-headers | vhd-format.0.12.2 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-headers | vhd-format.0.12.3 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-headers | vhd-format.0.9.1 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-headers | vhd-format.0.9.1 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | vhd-format.0.12.2 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | vhd-format.0.12.3 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | vhd-format.0.12.1 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | vhd-format.0.13.0 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | vhd-format.0.12.0 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |