| 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.3 | n/a | Unknown | CVE-2017-7542 | 7/21/2017 |
| linux-headers | vhd-format.0.13.0 | n/a | Unknown | CVE-2017-7542 | 7/21/2017 |
| linux-headers | vhd-format.0.9.1 | n/a | Unknown | CVE-2017-7542 | 7/21/2017 |
| linux-headers | vhd-format.0.12.1 | n/a | Unknown | CVE-2017-7542 | 7/21/2017 |
| linux-headers | vhd-format.0.12.0 | n/a | Unknown | CVE-2017-7542 | 7/21/2017 |
| linux-headers | vhd-format.0.12.2 | n/a | Unknown | CVE-2017-7542 | 7/21/2017 |
| linux-headers | vhd-format.0.9.1 | n/a | Unknown | CVE-2017-7541 | 7/25/2017 |
| linux-headers | vhd-format.0.13.0 | n/a | Unknown | CVE-2017-7541 | 7/25/2017 |
| linux-headers | vhd-format.0.12.3 | n/a | Unknown | CVE-2017-7541 | 7/25/2017 |
| linux-headers | vhd-format.0.12.2 | n/a | Unknown | CVE-2017-7541 | 7/25/2017 |
| linux-headers | vhd-format.0.12.0 | n/a | Unknown | CVE-2017-7541 | 7/25/2017 |
| linux-headers | vhd-format.0.12.1 | n/a | Unknown | CVE-2017-7541 | 7/25/2017 |
| linux-headers | vhd-format.0.12.0 | n/a | Unknown | CVE-2017-7533 | 8/5/2017 |
| linux-headers | vhd-format.0.12.1 | n/a | Unknown | CVE-2017-7533 | 8/5/2017 |
| linux-headers | vhd-format.0.12.3 | n/a | Unknown | CVE-2017-7533 | 8/5/2017 |
| linux-headers | vhd-format.0.13.0 | n/a | Unknown | CVE-2017-7533 | 8/5/2017 |
| linux-headers | vhd-format.0.12.2 | n/a | Unknown | CVE-2017-7533 | 8/5/2017 |
| linux-headers | vhd-format.0.9.1 | n/a | Unknown | CVE-2017-7533 | 8/5/2017 |
| linux-headers | vhd-format.0.9.1 | [UNKNOWN] | Medium | CVE-2017-7518 | 7/30/2018 |
| linux-headers | vhd-format.0.13.0 | [UNKNOWN] | Medium | CVE-2017-7518 | 7/30/2018 |