| 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 | Unknown | CVE-2020-8647 | 2/6/2020 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2020-8647 | 2/6/2020 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2020-8647 | 2/6/2020 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2020-8647 | 2/6/2020 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2020-8428 | 1/28/2020 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2020-8428 | 1/28/2020 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2020-8428 | 1/28/2020 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2020-8428 | 1/28/2020 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2020-8428 | 1/28/2020 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2020-8428 | 1/28/2020 |
| linux-headers | shell.v0.13.0 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | shell.v0.12.0 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | shell.v0.14.0 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | shell.v0.17.0 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | shell.v0.15.0 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | shell.v0.16.0 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | shell.v0.16.0 | Linux | Unknown | CVE-2020-36791 - net_sched: keep alloc_hash updated after hash allocation | 5/7/2025 |
| linux-headers | shell.v0.14.0 | Linux | Unknown | CVE-2020-36791 - net_sched: keep alloc_hash updated after hash allocation | 5/7/2025 |
| linux-headers | shell.v0.13.0 | Linux | Unknown | CVE-2020-36791 - net_sched: keep alloc_hash updated after hash allocation | 5/7/2025 |
| linux-headers | shell.v0.12.0 | Linux | Unknown | CVE-2020-36791 - net_sched: keep alloc_hash updated after hash allocation | 5/7/2025 |