← Search results
CVE-LINKED INVENTORY204 SECURITY RECORDS
IBM Corporation
AIX
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record IBM AIX. Use that record for publisher support phases and retirement dates.
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-2025-33112 | 10 Jun 2025 | 7.3; 4.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-56347 | 18 Mar 2025 | 7.2; 7.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-56346 | 18 Mar 2025 | 7.2; 7.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-52906 | 25 Dec 2024 | 7.2, 7.3, VIOS 3.1, 4.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-47102 | 25 Dec 2024 | 7.2; 7.3; 3.1; 4.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-47115 | 7 Dec 2024 | 7.2, 7.3, VIOS 3.1, VIOS 4.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-27260 | 16 May 2024 | 7.2, 7.3, VIOS 3.1, VIOS 4.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-27273 | 7 May 2024 | 7.2, 7.3, VIOS 3.1, VIOS 4.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-25021 | 22 Feb 2024 | 7.3, VIOS 4.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-45171 | 11 Jan 2024 | 7.2, 7.3, VIOS 3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-45169 | 11 Jan 2024 | 7.2, 7.3, VIOS 3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-45173 | 11 Jan 2024 | 7.2, 7.3, VIOS 3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-45175 | 11 Jan 2024 | 7.2, 7.3, VIOS 3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-45165 | 22 Dec 2023 | 7.2, 7.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-45172 | 19 Dec 2023 | 7.2, 7.3, VIOS 3.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-45170 | 13 Dec 2023 | 7.2, 7.3, VIOS 3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-45174 | 13 Dec 2023 | 7.2, 7.3, VIOS 3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-45166 | 13 Dec 2023 | 7.2, 7.3, VIOS 3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-45168 | 1 Dec 2023 | 7.2, 7.3, VIOS 3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-45167 | 10 Nov 2023 | 7.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-40371 | 24 Aug 2023 | 7.2, 7.3, VIOS 3.1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2023-28528 | 28 Apr 2023 | 7.1, 7.2, 7.3, VIOS 3.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-26286 | 26 Apr 2023 | 7.1, 7.2, 7.3, VIOS 3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-47990 | 18 Jan 2023 | 7.1, 7.2, 7.3, VIOS 3.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-2022-41290 | 23 Dec 2022 | 7.1, 7.2, 7.3, VIOS 3.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-2022-39164 | 23 Dec 2022 | 7.1, 7.2, 7.3, VIOS 3.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-2022-43849 | 23 Dec 2022 | 7.1, 7.2, 7.3, VIOS 3.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-2022-43848 | 23 Dec 2022 | 7.1, 7.2, 7.3, VIOS 3.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-2022-39165 | 23 Dec 2022 | 7.1, 7.2, 7.3, VIOS 3.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-2022-40233 | 23 Dec 2022 | 7.1, 7.2, 7.3, VIOS 3.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-2022-43380 | 23 Dec 2022 | 7.1, 7.2, 7.3, VIOS 3.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-2022-43381 | 23 Dec 2022 | 7.1, 7.2, 7.3, VIOS 3.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-2022-43382 | 20 Dec 2022 | 7.1, 7.2, 7.3, VIOS 3.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-2022-36768 | 13 Sep 2022 | 7.1; 7.2; 7.3; 3.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-2022-22444 | 15 Jun 2022 | 7.1; 7.2; 7.3; 3.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-2022-22351 | 7 Mar 2022 | 7.1; 7.2; 7.3; 3.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-2022-22350 | 2 Mar 2022 | 7.1; 7.2; 7.3; 3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-38995 | 24 Feb 2022 | 7.1; 7.2; 7.3; 3.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-2021-38994 | 24 Feb 2022 | 7.1; 7.2; 7.3; 3.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-2021-38991 | 11 Jan 2022 | 7.1; 7.2; 7.3; 3.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-2021-38990 | 7 Jan 2022 | 7.1; 7.2; 3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-29861 | 17 Nov 2021 | 7.1; 7.2; 3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-29727 | 26 Aug 2021 | 7.1; 7.2; 3.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-2021-29706 | 17 Jun 2021 | 7.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-2020-4887 | 20 Jan 2021 | 7.1; 7.2; 3.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-1655 | 22 Jun 2018 | 6.1; 5.3; 7.1; 7.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-1383 | 13 Feb 2018 | 6.1; 7.1; 7.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-1692 | 7 Feb 2018 | 6.1; 5.3; 7.1; 7.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-1541 | 3 Oct 2017 | 6.1; 5.3; 7.1; 7.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2016-8972 | 15 Feb 2017 | 6.1; 7.1; 7.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 ↗ |
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.