← Search results
CVE-LINKED INVENTORY123 SECURITY RECORDS
Linux
kernel:
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2022-3630 | 21 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3629 | 21 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3625 | 21 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3624 | 21 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3623 | 20 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3621 | 20 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3619 | 20 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3606 | 19 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3595 | 18 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3594 | 18 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3567 | 17 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3566 | 17 Oct 2022 | 4.19.316; 5.4.278; 5.10.220; 5.15.161 | 4.19.317; 5.4.279; 5.10.221; 5.15.162; 6.1 | Update reference ↗ |
| CVE-2022-3565 | 17 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3564 | 17 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3563 | 17 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3545 | 17 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3544 | 17 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3543 | 17 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3541 | 17 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3534 | 17 Oct 2022 | 5.10.162; 5.15.0; 5.15.1; 5.15.2; 5.15.3; 5.15.4; 5.15.5; 5.15.6 | 5.10.163; 5.15.86; 6.0.16; 6.1.2; 6.2 | Update reference ↗ |
| CVE-2022-3533 | 17 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3526 | 16 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3524 | 16 Oct 2022 | n/a | Update to V3.0.0 or later version | Update reference ↗ |
| CVE-2022-3523 | 16 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3521 | 16 Oct 2022 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-3435 | 8 Oct 2022 | n/a | Update to V1.3.0 or later version | Update reference ↗ |
| CVE-2022-36402 | 16 Sep 2022 | v4.3-rc1 < 5.13.0-52* | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-3176 | 16 Sep 2022 | unspecified < fc78b2fc21f10c4c9c4d5d659a685710ffa63659 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-40133 | 9 Sep 2022 | v4.20-rc1 < 5.13.0-52* | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-38457 | 9 Sep 2022 | v4.20-rc1 < 5.13.0-52* | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-38096 | 9 Sep 2022 | v4.20-rc1 < 5.13.0-52* | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2022-36280 | 9 Sep 2022 | v3.2-rc1 < 5.13.0-52* | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2021-4037 | 24 Aug 2022 | * < 5.4.241; 5.5 < 5.10.146 | 5.12; 0:4.18.0-372.9.1.rt7.166.el8 < *; 0:4.18.0-372.9.1.el8 < *; 0:4.18.0-305.49.1.rt7.121.el8_4 < *; 0:4.18.0-305.49.1.el8_4 < * | Update reference ↗ |
| CVE-2022-29581 | 17 May 2022 | unspecified < 5.18; 4.14 < unspecified | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-1116 | 17 May 2022 | unspecified < 5.4.189; 5.4.24 < unspecified | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-1353 | 29 Apr 2022 | < 4.9.311; 4.10 < 4.14.276; 4.15 < 4.19.238; 4.20 < 5.4.189; 5.5 < 5.10.110; 5.11 < 5.15.33; 5.16 < 5.16.19 | Update to V2.17.0 or later version | Update reference ↗ |
| CVE-2022-1055 | 29 Mar 2022 | 5.1.0 < 5.4.177; 5.5.0 < 5.10.97; 5.11.0 < 5.15.20; 5.16.0 < 5.16.6 | 5.17.0; 04c2a47ffb13c29778e2a14e414ad4cb5a5db4b5 | Update reference ↗ |
| CVE-2022-0995 | 25 Mar 2022 | kernel: kernel 5.17 rc8 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-0742 | 18 Mar 2022 | unspecified ≤ 5.13 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-0847 | 7 Mar 2022 | kernel: Linux Kernel 5.17 rc6 | Update to V2.17.0 or later version | Update reference ↗ |
| CVE-2022-0492 | 3 Mar 2022 | kernel: kernel 5.17 rc3 | Update to V2.17.0 or later version | Update reference ↗ |
| CVE-2021-4090 | 18 Feb 2022 | 5.11 < 5.15.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-0185 | 11 Feb 2022 | kernel: 8.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-22600 | 26 Jan 2022 | Kernel: unspecified < 5.4.168, unspecified < 5.10.88, unspecified < 5.15.11, unspecified < 5.16-rc6 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-34866 | 25 Jan 2022 | 5.14-rc3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-22555 | 7 Jul 2021 | Linux Kernel: 2.6.19-rc1 < unspecified | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-31440 | 21 May 2021 | 5.11.15 | For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. Additional Changes: For detailed information on changes in this release, see the Red Hat Enterprise Linux 8.5 Release Notes linked from the References section. For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. | Update reference ↗ |
| CVE-2021-3483 | 17 May 2021 | < 4.4.265; 4.5 < 4.9.265; 4.10 < 4.14.229; 4.15 < 4.19.185; 4.20 < 5.4.110; 5.5 < 5.10.28; 5.11 < 5.11.12 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3501 | 5 May 2021 | 5.9 < 5.10.32; 5.11 < 5.11.16 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-3493 | 17 Apr 2021 | linux kernel: 5.8 kernel < 5.8.0-50.56, 5.4 kernel < 5.4.0-72.80, 4.15 kernel < 4.15.0-142.146, 4.4 kernel < 4.4.0-209.241 | Apply https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7c03e2cda4a584cadc398e8f6641ca9988a39d52 | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.