| Version | |
|---|---|
| vhd-format-lwt.0.13.0 (latest) | |
| vhd-format-lwt.0.12.3 | |
| vhd-format-lwt.0.12.2 | |
| vhd-format-lwt.0.12.1 | |
| vhd-format-lwt.0.12.0 |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| linux-headers | vhd-format-lwt.0.13.0 | n/a | Critical | CVE-2022-47939 | 12/23/2022 |
| linux-headers | vhd-format-lwt.0.12.0 | n/a | Critical | CVE-2022-47939 | 12/23/2022 |
| linux-headers | vhd-format-lwt.0.12.2 | n/a | Critical | CVE-2022-47939 | 12/23/2022 |
| linux-headers | vhd-format-lwt.0.12.1 | n/a | Critical | CVE-2022-47939 | 12/23/2022 |
| linux-headers | vhd-format-lwt.0.12.3 | n/a | Critical | CVE-2022-47939 | 12/23/2022 |
| linux-headers | vhd-format-lwt.0.13.0 | n/a | Medium | CVE-2022-47938 | 12/23/2022 |
| linux-headers | vhd-format-lwt.0.12.3 | n/a | Medium | CVE-2022-47938 | 12/23/2022 |
| linux-headers | vhd-format-lwt.0.12.0 | n/a | Medium | CVE-2022-47938 | 12/23/2022 |
| linux-headers | vhd-format-lwt.0.12.1 | n/a | Medium | CVE-2022-47938 | 12/23/2022 |
| linux-headers | vhd-format-lwt.0.12.2 | n/a | Medium | CVE-2022-47938 | 12/23/2022 |
| linux-headers | vhd-format-lwt.0.12.0 | n/a | Medium | CVE-2022-47929 | 1/17/2023 |
| linux-headers | vhd-format-lwt.0.12.3 | n/a | Medium | CVE-2022-47929 | 1/17/2023 |
| linux-headers | vhd-format-lwt.0.13.0 | n/a | Medium | CVE-2022-47929 | 1/17/2023 |
| linux-headers | vhd-format-lwt.0.12.1 | n/a | Medium | CVE-2022-47929 | 1/17/2023 |
| linux-headers | vhd-format-lwt.0.12.2 | n/a | Medium | CVE-2022-47929 | 1/17/2023 |
| linux-headers | vhd-format-lwt.0.12.1 | n/a | High | CVE-2022-47521 | 12/18/2022 |
| linux-headers | vhd-format-lwt.0.12.0 | n/a | High | CVE-2022-47521 | 12/18/2022 |
| linux-headers | vhd-format-lwt.0.12.2 | n/a | High | CVE-2022-47521 | 12/18/2022 |
| linux-headers | vhd-format-lwt.0.12.3 | n/a | High | CVE-2022-47521 | 12/18/2022 |
| linux-headers | vhd-format-lwt.0.13.0 | n/a | High | CVE-2022-47521 | 12/18/2022 |