What is CVE-2023-20577?

CVE-2023-20577 is A heap overflow in SMM module may allow an attacker with access to a second vulnerability that enables writing to SPI flash, potentially…. The supplied enrichment data classifies it as Memory Corruption mapped to CWE-121 Stack-based Buffer Overflow.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Exploitation is reported, but no independent confirmation is available in the sources we have. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2023-20577 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

A public PoC is not confirmed from current sources for CVE-2023-20577. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with Not reported where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2023-20577 using CVSS 7.4, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

highMemory Corruption

CVE-2023-20577

CVE-2023-20577 — A heap overflow in SMM module may allow an attacker with access to a second vulnerability that enables writing to SPI flash, potentially…

A heap overflow in SMM module may allow an attacker with access to a second vulnerability that enables writing to SPI flash, potentially resulting in arbitrary code execution.

Published Sep 2, 2026Updated Sep 2, 2026Sources: NVD, AMD (CNA), GitHub, GitHub Security Advisory, Red Hat (VEX), SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Reported

not confirmed by CISA

EPSS

ahead of 0% of scored CVEs

Affects

AMD

39 products listed

CVSS base

7.4

high

Remediation

The vendor's own words where we have them.

Upgrade 2nd Gen AMD EPYC™ Processors to a fixed release (RomePI 1.0.0.H). Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

Red Hat VEX · CVE-2023-20577

fixed0affected0not affected59

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
AMD	2nd Gen AMD EPYC™ Processors	RomePI 1.0.0.H	Patched
AMD	3rd Gen AMD EPYC™ Processors	MilanPI 1.0.0.C	Patched
AMD	4th Gen AMD EPYC™ Processors	GenoaPI 1.0.0.8	Patched
AMD	AMD Instinct™ MI300A	MI300 SR5 PI 1.0.0.1	Patched
AMD	AMD Ryzen™ 3000 Series Desktop Processors	ComboAM4v2 1.2.0.B	Patched
AMD	AMD Ryzen™ 3000 Series Desktop Processors	ComboAM4 1.0.0.B	Patched
AMD	AMD Ryzen™ 5000 Series Desktop Processors	ComboAM4v2 1.2.0.B	Patched
AMD	AMD Ryzen™ 5000 Series Desktop Processors with Radeon™ Graphics	ComboAM4v2 1.2.0.B	Patched
AMD	AMD Ryzen™ 7000 Series Processors	ComboAM5 1.0.0.7b	Patched
AMD	AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics	ComboAM4v2 1.2.0.B	Patched
AMD	AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics	ComboAM4 1.0.0.B	Patched
AMD	AMD Ryzen™ 4000 Series Desktop Processors with Radeon™ Graphics	ComboAM4v2 1.2.0.B	Patched

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

High

Attack Vector

Local

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.4	CVSS 3.1	high	1.4	5.9	amd.com (CNA), AMD (CNA), GHSA, Red Hat (VEX)

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-121 · Stack-based Buffer Overflow

Modify Memory
DoS: Crash, Exit, or Restart
DoS: Resource Consumption (CPU)
DoS: Resource Consumption (Memory)

Mitigation: Run or compile the software using features or extensions that automatically provide a protection mechanism that mitigates or eliminates buffer overflows. For example, certain compilers and extensions provide automatic buffer overflow detection mechanisms that are built into the compiled code. Examples include the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice.

Weakness & attack patterns

CWE-121Stack-based Buffer Overflow

Inferred from the weakness class — not observed against this CVE.

CAPEC-100 · Overflow BuffersCAPEC-123 · Buffer Manipulation

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 7.4 (AV:L)
Sep 2, 2026 · NVD
Initial · CVE published
Sep 2, 2026 · NVD
Added · GHSA-hp78-wv22-mhmg published (high)
Sep 2, 2026 · GitHub Security Advisory
CVE published by MITRE.
Sep 2, 2026 · SOCRadar CTI
2023
CVE code is reserved.
Jan 1, 2023 · SOCRadar CTI

Source activity

Readings a source repeats on a schedule, counted rather than listed.

3×TweetsFeb 14, 2024 – Feb 16, 2024 · SOCRadar CTI
1×SVRS is calculatedMar 15, 2024 · SOCRadar CTI

References

6 on the record

www.amd.com/en/resources/product-security/bulletin/amd-sb-7009.html
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2023-20577
NVD
github.com/advisories/GHSA-hp78-wv22-mhmg
Exploit, Third Party Advisory
access.redhat.com/security/cve/CVE-2023-20577
Vendor Advisory
bugzilla.redhat.com/show_bug.cgi?id=2263392
Vendor Advisory
www.cve.org/CVERecord?id=CVE-2023-20577
Vendor Advisory

Elsewhere on this site

AMDevery CVE for this vendor
Memory Corruptionsame class
CWE-121other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2023-20577 is A heap overflow in SMM module may allow an attacker with access to a second vulnerability that enables writing to SPI flash, potentially…, a high vulnerability affecting 2nd Gen AMD EPYC™ Processors, 3rd Gen AMD EPYC™ Processors, 4th Gen AMD EPYC™ Processors, AMD Instinct™ MI300A, AMD Ryzen™ 3000 Series Desktop Processors, AMD Ryzen™ 5000 Series Desktop Processors, AMD Ryzen™ 5000 Series Desktop Processors with Radeon™ Graphics, AMD Ryzen™ 7000 Series Processors, AMD Athlon™ 3000 Series Desktop Processors with Radeon™ Graphics, AMD Ryzen™ 4000 Series Desktop Processors with Radeon™ Graphics, AMD Ryzen™ Threadripper™ 3000 Series Processors, AMD Ryzen™ Threadripper™ PRO 3000WX Series Processors, AMD Ryzen™ Threadripper™ PRO 5000WX Processors, AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics, AMD Ryzen™ 3000 Series Mobile Processor with Radeon™ Graphics, AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics, AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics, AMD Ryzen™ 7020 Series Processors with Radeon™ Graphics, AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics, AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics, AMD Ryzen™ 5000 Series Processors with Radeon™ Graphics, AMD Ryzen™ 3000 Series Processors with Radeon™ Graphics, AMD Ryzen™ 7040 Series Processors with Radeon™ Graphics, AMD Ryzen™ 7045 Series Mobile Processors, AMD EPYC™ Embedded 3000, AMD EPYC™ Embedded 7002, AMD EPYC™ Embedded 7003, AMD EPYC™ Embedded 9003, AMD Ryzen™ Embedded R1000, AMD Ryzen™ Embedded R2000, AMD Ryzen™ Embedded 5000, AMD Ryzen™ Embedded V1000, AMD Ryzen™ Embedded V2000, AMD Ryzen™ Embedded V3000 from AMD. The current evidence does not list it in CISA KEV, and the exploit status is: Exploitation is reported, but no independent confirmation is available in the sources we have. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2023-20577. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.4 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.