| 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.16.0 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | shell.v0.15.0 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | shell.v0.13.0 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | shell.v0.12.0 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | shell.v0.14.0 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | shell.v0.17.0 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | shell.v0.13.0 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | shell.v0.16.0 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | shell.v0.14.0 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | shell.v0.15.0 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | shell.v0.17.0 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | shell.v0.12.0 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | shell.v0.13.0 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | shell.v0.12.0 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | shell.v0.14.0 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | shell.v0.17.0 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | shell.v0.16.0 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | shell.v0.15.0 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | shell.v0.15.0 | Linux | Low | CVE-2022-3649 - Linux Kernel BPF inode.c nilfs_new_inode use after free | 10/21/2022 |
| linux-headers | shell.v0.17.0 | Linux | Low | CVE-2022-3649 - Linux Kernel BPF inode.c nilfs_new_inode use after free | 10/21/2022 |