vciy

CVE-2023-20569

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

A side channel vulnerability on some of the AMD CPUs may allow an attacker to influence the return address prediction

CVE-2023-205694 of 4 sources documented this
24

rank 24 = 2 + 12 + 0 + 10 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.07302  ·  without this subject the record ranks 22

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 4.7, from NVD  ·  without this subject the record ranks 12

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 24

How much of the world it touches

NVD CPE configurations

20 products in the CPE ranges  ·  without this subject the record ranks 14

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 24

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$223,000over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$223,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.07302 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.07302EPSSNOT IN KEVas of 2026-09-20
Severity4.7 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2023-08-09, 1115 days at 0.07, as of 2026-08-28. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running AMD Ryzen™ 3000 Series Desktop Processors? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachneeds local access · low privileges required · no user interaction · high attack complexityreceipt
ImpactComplete confidentiality lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-203 Observable Discrepancyreceipt
Published consequencesCWE-203: Confidentiality, Access Control: Read Application Data, Bypass Protection Mechanism; Confidentiality: Read Application Data[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchryzen comboam4v2pi_1.2.0.breceipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD4.7 MEDIUMreceipt
Exploit probability0.07302 · top 6% of all CVEsreceipt
Blast breadth3 products across 3 vendorsderived
Assigned byAMDreceipt
Recorded changes43 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productAMD Ryzen™ 3000 Series Desktop Processors; AMD Ryzen™ PRO 3000 Series Desktop Processors; AMD Ryzen™ 3000 Series Desktop Processors with Radeon™ Graphics…receipt
Published rangesfedoraproject fedora 37; fedoraproject fedora 38; debian linux 10.0; debian linux 11.0receipt
Show all 20 published ranges
fedoraproject fedora 37
fedoraproject fedora 38
debian linux 10.0
debian linux 11.0
debian linux 12.0
amd ryzen 9 5950x firmware < comboam4v2pi_1.2.0.b
amd ryzen 9 5900x firmware < comboam4v2pi_1.2.0.b
amd ryzen 9 5900 firmware < comboam4v2pi_1.2.0.b
amd ryzen 9 pro 5945 firmware < comboam4v2pi_1.2.0.b
amd ryzen 7 5800x3d firmware < comboam4v2pi_1.2.0.b
amd ryzen 7 5800x firmware < comboam4v2pi_1.2.0.b
amd ryzen 7 5800 firmware < comboam4v2pi_1.2.0.b
amd ryzen 7 5700x firmware < comboam4v2pi_1.2.0.b
amd ryzen 7 pro 5845 firmware < comboam4v2pi_1.2.0.b
amd ryzen 5 5600x3d firmware < comboam4v2pi_1.2.0.b
amd ryzen 5 5600x firmware < comboam4v2pi_1.2.0.b
amd ryzen 5 5600 firmware < comboam4v2pi_1.2.0.b
amd ryzen 5 pro 5645 firmware < comboam4v2pi_1.2.0.b
amd ryzen 7 5700 firmware < comboam4v2pi_1.2.0.b
amd ryzen 5 5500 firmware < comboam4v2pi_1.2.0.b

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

A side channel vulnerability on some of the AMD CPUs may allow an attacker to influence the return address prediction. This may result in speculative execution at an attacker-controlled address, potentially leading to information disclosure. receipt

NVD's analysis a second authority

severity
4.7 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
weakness
CWE-203
affected versions
fedoraproject fedora 37; fedoraproject fedora 38; debian linux 10.0; and 17 more, listed in full below

check it yourself amd.com xenbits.xen.org openwall.com comsec.ethz.ch lists.fedoraproject.org lists.fedoraproject.org +5 morereceipt

Movement the material steps

9 Aug 20230.00046
17 Mar 20250.00633 · scoring model v2025.03.14
15 Jun 20260.0616 · scoring model v2026.06.15
28 Aug 20260.07302
Show all 43 observations
9 Aug 20230.00046
10 Aug 20230.00044
22 Aug 20230.00122
27 Aug 20230.00121
15 Sep 20230.00042
21 Apr 20240.00043
14 Aug 20240.00059
27 Aug 20240.00060
12 Nov 20240.00070
31 Jan 20250.00092
15 Feb 20250.00070
17 Mar 20250.00633
29 Mar 20250.0504
30 Mar 20250.00633
23 May 20250.0065
5 Jun 20250.00633
15 Jun 20250.0065
17 Jun 20250.00633
20 Jul 20250.0065
2 Aug 20250.00633
21 Aug 20250.0065
3 Sep 20250.00633
24 Sep 20250.0065
7 Oct 20250.00633
18 Nov 20250.01423
21 Nov 20250.00633
22 Dec 20250.0065
4 Jan 20260.00633
30 Jan 20260.0065
19 Feb 20260.00633
22 Feb 20260.0065
7 Mar 20260.00633
21 Apr 20260.02007
22 Apr 20260.01954
28 Apr 20260.02007
11 May 20260.01954
22 May 20260.02007
1 Jun 20260.01954
4 Jun 20260.02081
15 Jun 20260.0616
20 Jul 20260.06657
9 Aug 20260.06713
28 Aug 20260.07302

43 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.07302Published2023-08-08Index as of2026-08-28

The record had been public for 3 years when this index was last written.

Published 2023-08-08 receipt · Index as of 2026-08-28 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2023-20569.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.