| Version | |
|---|---|
| core.v0.17.2 (latest) | |
| core.v0.17.1 | |
| core.v0.17.0 | |
| core.v0.16.2 | |
| core.v0.16.1 | |
| core.v0.16.0 | |
| core.v0.15.1 | |
| core.v0.15.0 | |
| core.v0.14.1 | |
| core.v0.14.0 | |
| core.v0.13.0 | |
| core.v0.12.4 | |
| core.v0.12.3 | |
| core.v0.12.2 |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| linux-headers | core.v0.13.0 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | core.v0.12.3 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | core.v0.12.2 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | core.v0.12.4 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | core.v0.14.0 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | core.v0.14.1 | n/a | Medium | CVE-2022-3707 | 3/6/2023 |
| linux-headers | core.v0.12.4 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | core.v0.12.3 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | core.v0.12.2 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | core.v0.14.0 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | core.v0.13.0 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | core.v0.14.1 | n/a | High | CVE-2022-36946 | 7/27/2022 |
| linux-headers | core.v0.13.0 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | core.v0.14.1 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | core.v0.14.0 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | core.v0.12.4 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | core.v0.12.2 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | core.v0.12.3 | n/a | Medium | CVE-2022-36879 | 7/27/2022 |
| linux-headers | core.v0.13.0 | Linux | Low | CVE-2022-3649 - Linux Kernel BPF inode.c nilfs_new_inode use after free | 10/21/2022 |
| linux-headers | core.v0.12.2 | Linux | Low | CVE-2022-3649 - Linux Kernel BPF inode.c nilfs_new_inode use after free | 10/21/2022 |