| 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.12.0 | n/a | Unknown | CVE-2023-51782 | 12/25/2023 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2023-51782 | 12/25/2023 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2023-51782 | 12/25/2023 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2023-51782 | 12/25/2023 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2023-51782 | 12/25/2023 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2023-51782 | 12/25/2023 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2023-51781 | 12/25/2023 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2023-51781 | 12/25/2023 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2023-51781 | 12/25/2023 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2023-51781 | 12/25/2023 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2023-51781 | 12/25/2023 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2023-51781 | 12/25/2023 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2023-51780 | 12/25/2023 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2023-51780 | 12/25/2023 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2023-51780 | 12/25/2023 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2023-51780 | 12/25/2023 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2023-51780 | 12/25/2023 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2023-51780 | 12/25/2023 |
| linux-headers | shell.v0.12.0 | Red Hat | High | CVE-2023-5178 - Kernel: use after free in nvmet_tcp_free_crypto in nvme | 11/1/2023 |
| linux-headers | shell.v0.17.0 | Red Hat | High | CVE-2023-5178 - Kernel: use after free in nvmet_tcp_free_crypto in nvme | 11/1/2023 |