← Search results
CVE-LINKED INVENTORY44 SECURITY RECORDS
Linux
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-2024-24864 | 5 Feb 2024 | v2.6.12-rc2 < v6.8-rc2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-24857 | 5 Feb 2024 | v4.0-rc1 < v6.8-rc2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-24858 | 5 Feb 2024 | v4.0-rc1 < v6.8-rc2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-24859 | 5 Feb 2024 | v4.0-rc1 < v6.8-rc2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-24860 | 5 Feb 2024 | v5.6-rc1 < v6.8-rc1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-24861 | 5 Feb 2024 | v3.1-rc1 < v6.8-rc1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-24855 | 5 Feb 2024 | v2.6.34-rc2 < v6.5-rc2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-23196 | 5 Feb 2024 | v5.6-rc1 < v6.5-rc1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-22386 | 5 Feb 2024 | v4.11-rc1 < v6.6-rc1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-21803 | 30 Jan 2024 | v2.6.12-rc2 < v6.8-rc1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-22099 | 25 Jan 2024 | v2.6.12-rc2 < v6.8-rc1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-23307 | 25 Jan 2024 | v4.1-rc1 < v6.8-rc1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-6931 | 19 Dec 2023 | 4.3.0 < 4.19.302; 4.20.0 < 5.4.264; 5.5.0 < 5.10.204; 5.11.0 < 5.15.143; 5.16.0 < 6.1.68; 6.2.0 < 6.6.7 | 6.7.0; 382c27f4ed28f803b1f1473ac2d8db0afc795a1b | Update reference ↗ |
| CVE-2023-2163 | 20 Sep 2023 | < 71b547f561247897a0a14f3082730156c0533fed | < 5.4 | Update reference ↗ |
| CVE-2023-35001 | 5 Jul 2023 | v3.13-rc1 | Update to V3.1.5 or later version | Update reference ↗ |
| CVE-2023-31248 | 5 Jul 2023 | v5.9-rc1 | Update to V1.3.0 or later version | Update reference ↗ |
| CVE-2023-3390 | 28 Jun 2023 | 3.16 < 4.14.322; 4.15 < 4.19.291; 4.20 < 5.4.251; 5.5 < 5.10.188; 5.11 < 5.15.118; 5.16 < 6.1.35; 6.2 < 6.3.9 | Update to V1.3.0 or later version | Update reference ↗ |
| CVE-2023-1295 | 28 Jun 2023 | 5.6 ≤ 5.11 | 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-2023-0459 | 25 May 2023 | 4b842e4e25b12951fa10dedb4bc16bc47e3b850c ≤ 74e19ef0ff8061ef55957c3abd71614ef0f42f47 | 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-2023-2235 | 1 May 2023 | 5.13 < 6.3 | 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-2023-2236 | 1 May 2023 | 5.19 < 6.1 | 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-2023-0458 | 26 Apr 2023 | ≤ 6.1.8 | 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-2023-0045 | 25 Apr 2023 | 9137bb27e60e < a664ec9158eeddd75121d39c9a0758016097fa96 | Update to V3.0.0 or later version | Update reference ↗ |
| CVE-2023-1998 | 21 Apr 2023 | < 6.3 | 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-2023-1872 | 12 Apr 2023 | 5.7 ≤ 5.17 | 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-2023-1829 | 12 Apr 2023 | 3.8.0 < 4.14.308; 4.15.0 < 4.19.276; 4.20.0 < 5.4.235; 5.5.0 < 5.10.173; 5.11.0 < 5.15.100; 5.16.0 < 6.1.18; 6.2.0 < 6.2.5 | 6.3.0; 8c710f75256bb3cf05ac7b1672c82b92c43f3d28 | Update reference ↗ |
| CVE-2023-1281 | 22 Mar 2023 | 4.14.0 < 5.10.169; 5.11.0 < 5.15.95; 5.16.0 < 6.1.13 | 6.2.0; ee059170b1f7e94e55fa6cadee544e176a6e59c2 | Update reference ↗ |
| CVE-2023-0461 | 28 Feb 2023 | < 2c02d41d71f90a5168391b6a5f2954112ba2307c | 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-2023-23586 | 17 Feb 2023 | 5.6 ≤ 5.10.161 | 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-2023-0240 | 30 Jan 2023 | 5.10 ≤ 5.10.161 | 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-4696 | 11 Jan 2023 | 5.7-rc1 ≤ 5.10.159 | 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-2196 | 9 Jan 2023 | 64b8f33b2e1e687d465b5cb382e7bec495f1e026 < f93a1a5bdcdd122aae0a3eab7a52c15b71fb725b; e089a83fbc55b8057f332c00f125acaa02b08ef7 < 2e7eab81425ad6c875f2ed47c0ce01e78afc38a5; 02a3868d18fe639363f1cea6e6d7914513198e43 < 2e7eab81425ad6c875f2ed47c0ce01e78afc38a5; 5c911beff20aa8639e7a1f28988736c13e03ed54 < 1b0cafaae8884726c597caded50af185ffc13349; 5c911beff20aa8639e7a1f28988736c13e03ed54 < 6b539a7dbb49250f92515c2ba60aea239efc9e35; 5c911beff20aa8639e7a1f28988736c13e03ed54 < 63fada296062e91ad9f871970d4e7f19e21a6a15; 5c911beff20aa8639e7a1f28988736c13e03ed54 < 2e7eab81425ad6c875f2ed47c0ce01e78afc38a5; 5.4.47 < 5.4.233 | 6.2.0 | Update reference ↗ |
| CVE-2022-42896 | 23 Nov 2022 | 3.0.0 ≤ 711f8c3fb3db61897080468586b970c87c61d9e4 | 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-42895 | 23 Nov 2022 | 3.0.0 ≤ b1a2cd50c0357f243b7435a732b4e62ba3157a2e | 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-3910 | 22 Nov 2022 | 5.18.0 ≤ 5.19.10 | 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-43945 | 4 Nov 2022 | < 6.0.2 | 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-3491 | 4 Jun 2021 | trunk < v5.13-rc4; linux-5.12.y < v5.12.4; linux-5.11.y < v5.11.21; linux-5.10.y < v5.10.37; v5.7-rc1 < 5.7* | 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-3490 | 4 Jun 2021 | trunk < v5.13-rc4; linux-5.12.y < v5.12.4; linux-5.11.y < v5.11.21; linux-5.10.y < v5.10.37; v5.7-rc1 < 5.7* | 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-3489 | 4 Jun 2021 | trunk < v5.13-rc4; linux-5.12.y < v5.12.4; linux-5.11.y < v5.11.21; linux-5.10.y < v5.10.37; v5.8 < 5.8* | 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-2019-3016 | 31 Jan 2020 | 4.10 to 5.6 | 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-2019-11479 | 18 Jun 2019 | 4.4 < 4.4.182; 4.9 < 4.9.182; 4.14 < 4.14.127; 4.19 < 4.19.52; 5.1 < 5.1.11 | Update to V1.1.5 or later version | Update reference ↗ |
| CVE-2019-11478 | 18 Jun 2019 | 4.4 < 4.4.182; 4.9 < 4.9.182; 4.14 < 4.14.127; 4.19 < 4.19.52; 5.1 < 5.1.11 | Update to V1.1.5 or later version | Update reference ↗ |
| CVE-2019-11477 | 18 Jun 2019 | 4.4 < 4.4.182; 4.9 < 4.9.182; 4.14 < 4.14.127; 4.19 < 4.19.52; 5.1 < 5.1.11 | Update to V1.1.5 or later version | Update reference ↗ |
| CVE-2018-5390 | 6 Aug 2018 | 4.9 < 4.9* | 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 ↗ |
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.