| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| linux-headers | mirage-block-unix.2.8.2 | n/a | Medium | CVE-2022-41848 | 9/30/2022 |
| linux-headers | mirage-block-unix.2.11.0 | n/a | Medium | CVE-2022-41848 | 9/30/2022 |
| kernel-headers | mirage-block-unix.2.9.0 | n/a | Medium | CVE-2022-41848 | 9/30/2022 |
| kernel-headers | mirage-block-unix.2.10.0 | n/a | Medium | CVE-2022-41848 | 9/30/2022 |
| kernel-headers | mirage-block-unix.2.8.4 | n/a | Medium | CVE-2022-41848 | 9/30/2022 |
| linux-libc-dev | mirage-block-unix.2.8.4 | n/a | Medium | CVE-2022-41848 | 9/30/2022 |
| linux-headers | mirage-block-unix.2.9.0 | n/a | Medium | CVE-2022-41848 | 9/30/2022 |
| linux-headers | mirage-block-unix.2.11.1 | n/a | Medium | CVE-2022-41848 | 9/30/2022 |
| linux-libc-dev | mirage-block-unix.2.10.0 | n/a | Medium | CVE-2022-41848 | 9/30/2022 |
| linux-libc-dev | mirage-block-unix.2.9.0 | n/a | Medium | CVE-2022-41848 | 9/30/2022 |
| linux-libc-dev | mirage-block-unix.2.9.0 | n/a | High | CVE-2022-41674 | 10/13/2022 |
| linux-libc-dev | mirage-block-unix.2.8.4 | n/a | High | CVE-2022-41674 | 10/13/2022 |
| linux-headers | mirage-block-unix.2.11.1 | n/a | High | CVE-2022-41674 | 10/13/2022 |
| linux-headers | mirage-block-unix.2.9.0 | n/a | High | CVE-2022-41674 | 10/13/2022 |
| kernel-headers | mirage-block-unix.2.9.0 | n/a | High | CVE-2022-41674 | 10/13/2022 |
| linux-headers | mirage-block-unix.2.10.0 | n/a | High | CVE-2022-41674 | 10/13/2022 |
| linux-libc-dev | mirage-block-unix.2.10.0 | n/a | High | CVE-2022-41674 | 10/13/2022 |
| linux-headers | mirage-block-unix.2.8.2 | n/a | High | CVE-2022-41674 | 10/13/2022 |
| kernel-headers | mirage-block-unix.2.10.0 | n/a | High | CVE-2022-41674 | 10/13/2022 |
| linux-headers | mirage-block-unix.2.8.4 | n/a | High | CVE-2022-41674 | 10/13/2022 |