Product added
Showing changes seen on 2025-09-25. Every day
One change, in full: Product added: 29 products named as affected in CVE-2024-36353. The same change in 1 CVE record, across 29 products: 29 rows in all. Back to the ledger
| 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 changed | Days 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. |
|---|---|---|---|---|
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd athlon™ 3000 series mobile processors with radeon™ graphics | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd radeon™ pro v520 | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd radeon™ pro v620 | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd radeon™ pro v710 | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd radeon™ rx 5000/pro w5000 series graphics products | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd radeon™ rx 7000/pro w7000 series graphics products | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd radeon™ rx6000/pro w6000 series graphics products | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen embedded v2000a series processors | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ 4000 series desktop processors | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ 4000 series mobile processors with radeon™ graphics | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ 5000 series desktop processors with radeon™ graphics | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ 5000 series mobile processors with radeon™ graphics | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ 6000 series processors with radeon™ graphics | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ 7000 series desktop processor | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ 7020 series processors with radeon™ graphics | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ 7030 series mobile processors with radeon™ graphics | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ 7035 series processors with radeon™ graphics | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ 7040 series mobile processors with radeon™ graphics | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ 7045 series mobile processors with radeon™ graphics | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ 8000 series desktop processors | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ 9000 series desktop processors | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ 9000hx series processors | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ ai max 300 series processors | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ embedded v1000 series processors (formerly codenamed "raven ridge") | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names amd ryzen™ z2 series processors extreme | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names ryzen™ embedded r1000 | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names ryzen™ embedded r2000 | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names ryzen™ embedded v2000 | Time to revision 207 days | |
| 2025-09-25 | CVE-2024-36353 | not named as affected at publication, now names ryzen™ embedded v3000 | Time to revision 207 days |
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.
What this page cannot see
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 →
Paste your closed CVE tickets and see which of these changes hit them →