Skip to content

Product added

What a record said when it was published, what it says now, and the commit that changed it.

79 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes of "Product added" published by AMD, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.Record, Which record was edited, by its CVE id, or how many records one collapsed line stands on.Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry.What changedDays to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong.
Sun 23 Nov 2025· 3 record changes
2025-11-23CVE-2025-62626not named as affected at publication, now names amd epyc™ 9005 series processorsDays to revision 2
2025-11-23CVE-2023-20599not named as affected at publication, now names amd athlon™ 3000 series mobile processors with radeon™ graphicsDays to revision 166
2025-11-23CVE-2023-20599not named as affected at publication, now names amd ryzen™ embedded v1000 series processorsDays to revision 166
Fri 21 Nov 2025· 2 record changes
2025-11-21CVE-2023-20599not named as affected at publication, now names amd ryzen™ embedded r1000 series processorsDays to revision 164
2025-11-21CVE-2023-20599not named as affected at publication, now names amd ryzen™ embedded r2000 series processorsDays to revision 164
Thu 25 Sep 2025· 29 record changes
2025-09-25CVE-2024-36353not named as affected at publication, now names amd athlon™ 3000 series mobile processors with radeon™ graphicsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd radeon™ pro v520Days to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd radeon™ pro v620Days to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd radeon™ pro v710Days to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd radeon™ rx 5000/pro w5000 series graphics productsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd radeon™ rx 7000/pro w7000 series graphics productsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd radeon™ rx6000/pro w6000 series graphics productsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen embedded v2000a series processorsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ 4000 series desktop processorsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ 4000 series mobile processors with radeon™ graphicsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ 5000 series desktop processors with radeon™ graphicsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ 5000 series mobile processors with radeon™ graphicsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ 6000 series processors with radeon™ graphicsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ 7000 series desktop processorDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ 7020 series processors with radeon™ graphicsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ 7030 series mobile processors with radeon™ graphicsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ 7035 series processors with radeon™ graphicsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ 7040 series mobile processors with radeon™ graphicsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ 7045 series mobile processors with radeon™ graphicsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ 8000 series desktop processorsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ 9000 series desktop processorsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ 9000hx series processorsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ ai max 300 series processorsDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ embedded v1000 series processors (formerly codenamed "raven ridge")Days to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names amd ryzen™ z2 series processors extremeDays to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names ryzen™ embedded r1000Days to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names ryzen™ embedded r2000Days to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names ryzen™ embedded v2000Days to revision 207
2025-09-25CVE-2024-36353not named as affected at publication, now names ryzen™ embedded v3000Days to revision 207
Mon 30 Jun 2025· 8 record changes
2025-06-30CVE-2025-0036not named as affected at publication, now names alveo v80 compute acceleratorDays to revision 21
2025-06-30CVE-2025-0036not named as affected at publication, now names versal adaptive soc devicesDays to revision 21
2025-06-30CVE-2025-0036not named as affected at publication, now names versal ai core seriesDays to revision 21
2025-06-30CVE-2025-0036not named as affected at publication, now names versal ai edge seriesDays to revision 21
2025-06-30CVE-2025-0036not named as affected at publication, now names versal hbm seriesDays to revision 21
2025-06-30CVE-2025-0036not named as affected at publication, now names versal premium seriesDays to revision 21
2025-06-30CVE-2025-0036not named as affected at publication, now names versal prime seriesDays to revision 21
2025-06-30CVE-2025-0036not named as affected at publication, now names versal rf seriesDays to revision 21
Fri 27 Jun 2025· 14 record changes
2025-06-27CVE-2024-0179not named as affected at publication, now names amd ryzen™ embedded 5000Days to revision 136
2025-06-27CVE-2024-0179not named as affected at publication, now names amd ryzen™ embedded 7000Days to revision 136
2025-06-27CVE-2024-0179not named as affected at publication, now names amd ryzen™ embedded r1000Days to revision 136
2025-06-27CVE-2024-0179not named as affected at publication, now names amd ryzen™ embedded v1000Days to revision 136
2025-06-27CVE-2024-0179not named as affected at publication, now names amd ryzen™embedded r2000Days to revision 136
2025-06-27CVE-2024-21925not named as affected at publication, now names amd ryzen™ embedded r1000Days to revision 136
2025-06-27CVE-2024-21925not named as affected at publication, now names amd ryzen™ embedded r2000Days to revision 136
2025-06-27CVE-2024-21925not named as affected at publication, now names amd ryzen™ embedded v1000Days to revision 136
2025-06-27CVE-2023-20597not named as affected at publication, now names amd epyc™ embedded 7003Days to revision 646
2025-06-27CVE-2023-20597not named as affected at publication, now names amd ryzen™ embedded 5000Days to revision 646
2025-06-27CVE-2023-20597not named as affected at publication, now names amd ryzen™ embedded v2000Days to revision 646
2025-06-27CVE-2023-20597not named as affected at publication, now names amd ryzen™ embedded v3000Days to revision 646
2025-06-27CVE-2023-20594not named as affected at publication, now names amd ryzen™ embedded 7000Days to revision 646
2025-06-27CVE-2023-20594not named as affected at publication, now names amd ryzen™ embedded v3000Days to revision 646
Tue 11 Feb 2025· 2 record changes
2025-02-11CVE-2023-31356not named as affected at publication, now names amd epyc™ embedded 7003Days to revision 182
2025-02-11CVE-2023-31356not named as affected at publication, now names amd epyc™ embedded 9004Days to revision 182
Tue 18 Jun 2024· 4 record changes
2024-06-18CVE-2023-20533not named as affected at publication, now names amd epyc™ embedded 7002Days to revision 217
2024-06-18CVE-2023-20533not named as affected at publication, now names amd epyc™ embedded 7003Days to revision 217
2024-06-18CVE-2023-20566not named as affected at publication, now names amd epyc™ embedded 7003Days to revision 217
2024-06-18CVE-2023-20566not named as affected at publication, now names amd epyc™ embedded 9003Days to revision 217
Tue 13 Feb 2024· 17 record changes
2024-02-13CVE-2023-20521not named as affected at publication, now names amd epyc™ embedded 3000Days to revision 91
2024-02-13CVE-2023-20521not named as affected at publication, now names amd epyc™ embedded 7002Days to revision 91
2024-02-13CVE-2023-20521not named as affected at publication, now names amd epyc™ embedded 7003Days to revision 91
2024-02-13CVE-2023-20521not named as affected at publication, now names amd ryzen™ embedded r1000Days to revision 91
2024-02-13CVE-2023-20521not named as affected at publication, now names amd ryzen™ embedded r2000Days to revision 91
2024-02-13CVE-2023-20521not named as affected at publication, now names amd ryzen™ embedded v1000Days to revision 91
2024-02-13CVE-2023-20526not named as affected at publication, now names amd epyc™ embedded 3000Days to revision 91
2024-02-13CVE-2023-20526not named as affected at publication, now names amd epyc™ embedded 7002Days to revision 91
2024-02-13CVE-2023-20526not named as affected at publication, now names amd epyc™ embedded 7003Days to revision 91
2024-02-13CVE-2023-20533not named as affected at publication, now names amd epyc™ embedded 7002Days to revision 91
2024-02-13CVE-2023-20533not named as affected at publication, now names amd epyc™ embedded 7003Days to revision 91
2024-02-13CVE-2023-20533not named as affected at publication, now names amd ryzen™ embedded 5000Days to revision 91
2024-02-13CVE-2023-20563not named as affected at publication, now names amd ryzen™ embedded 5000Days to revision 91
2024-02-13CVE-2023-20563not named as affected at publication, now names amd ryzen™ embedded r1000Days to revision 91
2024-02-13CVE-2023-20563not named as affected at publication, now names amd ryzen™ embedded r2000Days to revision 91
2024-02-13CVE-2023-20563not named as affected at publication, now names amd ryzen™ embedded v3000Days to revision 91
2024-02-13CVE-2023-20565not named as affected at publication, now names amd ryzen™ embedded v3000Days to revision 91

This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
3,898 records with a counted edit in the 52 weeks to 7 Sep 2026 · snapshot built 03:47 UTC · scroll for earlierfewermore

Data sources and quality

Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.

A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.

The units, the refusals, the cut-offs and every source, in full →

Check my CVEs against these changes →