← Search results
CVE-LINKED INVENTORY105 SECURITY RECORDS
Publisher not identified
Intel(R) processors
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-2026-20917 | 11 Aug 2026 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-20760 | 11 Aug 2026 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-20716 | 11 Aug 2026 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-35979 | 12 May 2026 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-20109 | 12 Aug 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-45332 | 13 May 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-28956 | 13 May 2025 | Intel(R) Processors: See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-20103 | 13 May 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-20054 | 13 May 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-28693 | 14 Feb 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-31068 | 12 Feb 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-39355 | 12 Feb 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-28047 | 12 Feb 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-31157 | 12 Feb 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-39279 | 12 Feb 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-28127 | 12 Feb 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-29214 | 12 Feb 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-24582 | 12 Feb 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-34440 | 12 Feb 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-43758 | 12 Feb 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-21859 | 12 Feb 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-31155 | 12 Feb 2025 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-36242 | 13 Nov 2024 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-23984 | 16 Sep 2024 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-24968 | 16 Sep 2024 | See references | For OpenShift Container Platform 4.16 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.openshift.com/container-platform/4.16/release_notes/ocp-4-16-release-notes.html You may download the oc tool and use it to inspect release image metadata for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha values for the release are as follows: (For x86_64 architecture) The image digest is sha256:6be262c95acd928771f39e50afc7f1a628d5e20a2ba8c9a83a176c8eff809c06 (For s390x architecture) The image digest is sha256:d5fade25cc327a0f1b2174e9588ade616e4c240434e6a5e86088a2e5e9073431 (For ppc64le architecture) The image digest is sha256:8404b9ab00ca563e234145c0c7ab8f23600ad768639c5d28b56efec709db95eb (For aarch64 architecture) The image digest is sha256:284e30f29de4ca6220aadc4a691045d61b324308e51e3d5ddaf71d82bce8e816 All OpenShift Container Platform 4.16 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.openshift.com/container-platform/4.16/updating/updating_a_cluster/updating-cluster-cli.html | Update reference ↗ |
| CVE-2024-21829 | 16 Sep 2024 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-45733 | 16 May 2024 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-32282 | 14 Mar 2024 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-39368 | 14 Mar 2024 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-38575 | 14 Mar 2024 | some Intel(R) Processors | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-22329 | 14 Nov 2023 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-25756 | 14 Nov 2023 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-23583 | 14 Nov 2023 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-40982 | 11 Aug 2023 | See references | Update to V1.1.2 or later version | Update reference ↗ |
| CVE-2022-43505 | 11 Aug 2023 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-27879 | 11 Aug 2023 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-38083 | 11 Aug 2023 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-44611 | 11 Aug 2023 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-37343 | 11 Aug 2023 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-38087 | 10 May 2023 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-33894 | 10 May 2023 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-30704 | 16 Feb 2023 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-26837 | 16 Feb 2023 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-32231 | 16 Feb 2023 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-30539 | 16 Feb 2023 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-26343 | 16 Feb 2023 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-0187 | 16 Feb 2023 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-21198 | 11 Nov 2022 | See references | Update to V21.01.19 or later version | Update reference ↗ |
| CVE-2022-26006 | 11 Nov 2022 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2021-33060 | 18 Aug 2022 | See references | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
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.