| Version | |
|---|---|
| shell.v0.17.0 (latest) | |
| shell.v0.16.0 | |
| shell.v0.15.0 | |
| shell.v0.14.0 | |
| shell.v0.13.0 | |
| shell.v0.12.0 |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2022-39190 | 9/2/2022 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2022-39190 | 9/2/2022 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2022-39190 | 9/2/2022 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2022-39190 | 9/2/2022 |
| linux-headers | shell.v0.15.0 | n/a | High | CVE-2022-39189 | 9/2/2022 |
| linux-headers | shell.v0.16.0 | n/a | High | CVE-2022-39189 | 9/2/2022 |
| linux-headers | shell.v0.17.0 | n/a | High | CVE-2022-39189 | 9/2/2022 |
| linux-headers | shell.v0.12.0 | n/a | High | CVE-2022-39189 | 9/2/2022 |
| linux-headers | shell.v0.13.0 | n/a | High | CVE-2022-39189 | 9/2/2022 |
| linux-headers | shell.v0.14.0 | n/a | High | CVE-2022-39189 | 9/2/2022 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2022-39188 | 9/2/2022 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2022-39188 | 9/2/2022 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2022-39188 | 9/2/2022 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2022-39188 | 9/2/2022 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2022-39188 | 9/2/2022 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2022-39188 | 9/2/2022 |
| linux-headers | shell.v0.13.0 | Linux | High | CVE-2022-3910 - Use after free in IO_uring in the Linux Kernel | 11/22/2022 |
| linux-headers | shell.v0.17.0 | Linux | High | CVE-2022-3910 - Use after free in IO_uring in the Linux Kernel | 11/22/2022 |
| linux-headers | shell.v0.12.0 | Linux | High | CVE-2022-3910 - Use after free in IO_uring in the Linux Kernel | 11/22/2022 |
| linux-headers | shell.v0.14.0 | Linux | High | CVE-2022-3910 - Use after free in IO_uring in the Linux Kernel | 11/22/2022 |