amd epyc 7251 firmware
ProduktUScpe:2.3:o:amd:epyc_7251_firmware:*:*:*:*:*:*:*:*
Ein im Bedrohungsgraphen erfasstes Produkt; die Schwachstellen unten betreffen es bekanntermaßen.
nach Schweregrad
2critical13high24medium1low
aktualisiert 2026-10-27
| ID | Schweregrad CVSS-Basis-Schweregrad und -Wert (0–10). | EPSS FIRST.org-Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen, mit Perzentil-Rang unter allen CVEs. | ausnutzbar Auf CISAs Liste bekannter ausgenutzter Schwachstellen (KEV) oder ein öffentlicher Exploit liegt vor. | behoben Ob für einen betroffenen Bereich eine behobene Version vorliegt. | veröffentlicht | betroffen |
|---|
| CVE-2022-29900US | medium6.5 | 3.94% (90th) | Exploit | ✗kein Fix | 2022-07-12 | — |
| CVE-2023-20588US | medium5.5 | 11.2% (96th) | — | ✗kein Fix | 2023-08-08 | — |
| CVE-2022-23823US | medium6.5 | 1.17% (67th) | — | ✗kein Fix | 2022-06-15 | — |
| CVE-2021-26322US | high7.5OT erhöht | 1.05% (64th) | — | ✓naplespi-sp3_1.0.0.g | 2021-11-16 | < naplespi-sp3_1.0.0.g |
| CVE-2020-12988US | high7.5 | 1.04% (64th) | — | ✓naplespi-sp3_1.0.0.g | 2021-06-11 | < naplespi-sp3_1.0.0.g |
| CVE-2023-20592US | medium6.5 | 1.02% (63rd) | — | ✗kein Fix | 2023-11-14 | — |
| CVE-2023-20575US | medium6.5 | 0.80% (57th) | — | ✗kein Fix | 2023-07-11 | — |
| CVE-2023-20520US | critical9.8 | 0.79% (56th) | — | ✗kein Fix | 2023-05-09 | = naplespi_1.0.0.h |
| CVE-2022-23825US | medium6.5 | 0.78% (56th) | — | ✗kein Fix | 2022-07-14 | — |
| CVE-2021-46756US | critical9.1 | 0.65% (51st) | — | ✗kein Fix | 2023-05-09 | = naplespi_1.0.0.j |
| CVE-2023-20527US | medium6.5 | 0.61% (49th) | — | ✓naplespi_1.0.0.g | 2023-01-11 | < naplespi_1.0.0.g |
| CVE-2022-23824US | medium5.5 | 0.60% (48th) | — | ✗kein Fix | 2022-11-09 | — |
| CVE-2021-46774US | high7.5 | 0.51% (43rd) | — | ✓naplespi_1.0.0.k | 2023-11-14 | < naplespi_1.0.0.k |
| CVE-2021-26406US | high7.5 | 0.42% (36th) | — | ✗kein Fix | 2023-05-09 | = naplespi_1.0.0.e |
| CVE-2021-26356US | high7.4 | 0.40% (34th) | — | ✓naplespi_1.0.0.h | 2023-05-09 | < naplespi_1.0.0.h |
| CVE-2020-12944US | high7.8 | 0.35% (28th) | — | ✓naplespi-sp3_1.0.0.g | 2021-11-16 | < naplespi-sp3_1.0.0.g |
| CVE-2021-46744US | medium6.5 | 0.33% (27th) | — | ✗kein Fix | 2022-05-11 | — |
| CVE-2021-26341US | medium6.5 | 0.32% (25th) | — | ✗kein Fix | 2022-03-11 | — |
| CVE-2020-12966US | medium5.5 | 0.31% (24th) | — | ✗kein Fix | 2022-02-04 | — |
| CVE-2023-20526US | medium4.6 | 0.31% (24th) | — | ✓naplespi_1.0.0.h | 2023-11-14 | < naplespi_1.0.0.h |
| CVE-2021-26335US | high7.8 | 0.29% (22nd) | — | ✓naplespi-sp3_1.0.0.g | 2021-11-16 | < naplespi-sp3_1.0.0.g |
| CVE-2021-26331US | high7.8 | 0.29% (22nd) | — | ✓naplespi-sp3_1.0.0.g | 2021-11-16 | < naplespi-sp3_1.0.0.g |
| CVE-2021-26401US | medium5.6 | 0.29% (22nd) | — | ✗kein Fix | 2022-03-11 | — |
| CVE-2021-26408US | high7.1 | 0.27% (19th) | — | ✓naplespi-sp3_1.0.0.g | 2022-05-10 | < naplespi-sp3_1.0.0.g |
| CVE-2023-20521US | medium5.7 | 0.26% (18th) | — | ✓naplespi_1.0.0.h | 2023-11-14 | < naplespi_1.0.0.h |
| CVE-2021-26321US | medium5.5 | 0.25% (17th) | — | ✓naplespi-sp3_1.0.0.g | 2021-11-16 | < naplespi-sp3_1.0.0.g |
| CVE-2021-26340US | high8.4 | 0.25% (16th) | — | ✗kein Fix | 2021-12-10 | — |
| CVE-2021-26312US | medium5.5 | 0.25% (16th) | — | ✓naplespi-sp3_1.0.0.g | 2021-11-16 | < naplespi-sp3_1.0.0.g |
| CVE-2021-46778US | medium5.6 | 0.24% (15th) | — | ✗kein Fix | 2022-08-10 | — |
| CVE-2020-12954US | medium5.5 | 0.23% (14th) | — | ✓naplespi-sp3_1.0.0.g | 2021-11-16 | < naplespi-sp3_1.0.0.g |
| CVE-2021-26342US | low3.3 | 0.22% (13th) | — | ✓naplespi-sp3_1.0.0.h | 2022-05-11 | < naplespi-sp3_1.0.0.h |
| CVE-2021-26398US | high7.8 | 0.22% (13th) | — | ✓naplespi_1.0.0.h | 2023-01-11 | < naplespi_1.0.0.h |
| CVE-2021-26330US | medium5.5 | 0.22% (12th) | — | ✓naplespi-sp3_1.0.0.g | 2021-11-16 | < naplespi-sp3_1.0.0.g |
| CVE-2021-26329US | medium5.5 | 0.22% (12th) | — | ✓naplespi-sp3_1.0.0.g | 2021-11-16 | < naplespi-sp3_1.0.0.g |
| CVE-2020-12951US | high7.0 | 0.22% (12th) | — | ✓naplespi-sp3_1.0.0.g | 2021-11-16 | < naplespi-sp3_1.0.0.g |
| CVE-2021-26371US | medium5.5 | 0.19% (8th) | — | ✓naplespi_1.0.0.h | 2023-05-09 | < naplespi_1.0.0.h |
| CVE-2021-26320US | medium5.5 | 0.19% (8th) | — | ✓naplespi-sp3_1.0.0.g | 2021-11-16 | < naplespi-sp3_1.0.0.g |
| CVE-2021-26344US | high8.2 | 0.16% (5th) | — | ✗kein Fix | 2024-08-13 | — |
| CVE-2021-26403US | medium6.5OT erhöht | 0.13% (2nd) | — | ✓naplespi_1.0.0.e | 2023-01-11 | < naplespi_1.0.0.e |
| CVE-2023-20578US | medium6.4 | 0.12% (2nd) | — | ✓naplespi_1.0.0.k | 2024-08-13 | < naplespi_1.0.0.k |