Improper input validation in the SMM Supervisor may allow an attacker with a compromised SMI handler to gain Ring0 access potentially leadin
Improper input validation in the SMM Supervisor may allow an attacker with a compromised SMI handler to gain Ring0 access potentially leading to arbitrary code execution.
- Published
- Nov 14, 2023
- Updated
- Jun 17, 2026
- EPSS
- 1.0% · 63th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| amd | ryzen 7 5700g firmware | cpe:2.3:o:amd:ryzen_7_5700g_firmware |
| amd | ryzen 7 5700g | cpe:2.3:h:amd:ryzen_7_5700g |
| amd | ryzen 7 5700ge firmware | cpe:2.3:o:amd:ryzen_7_5700ge_firmware |
| amd | ryzen 7 5700ge | cpe:2.3:h:amd:ryzen_7_5700ge |
| amd | ryzen 5 5600g firmware | cpe:2.3:o:amd:ryzen_5_5600g_firmware |
| amd | ryzen 5 5600g | cpe:2.3:h:amd:ryzen_5_5600g |
| amd | ryzen 5 5600ge firmware | cpe:2.3:o:amd:ryzen_5_5600ge_firmware |
| amd | ryzen 5 5600ge | cpe:2.3:h:amd:ryzen_5_5600ge |
| amd | ryzen 3 5300g firmware | cpe:2.3:o:amd:ryzen_3_5300g_firmware |
| amd | ryzen 3 5300g | cpe:2.3:h:amd:ryzen_3_5300g |
| amd | ryzen 3 5300ge firmware | cpe:2.3:o:amd:ryzen_3_5300ge_firmware |
| amd | ryzen 3 5300ge | cpe:2.3:h:amd:ryzen_3_5300ge |
and 116 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd ryzen 3 5125c firmwarebefore cezannepi-fp6_1.0.0.fa
- amd ryzen 3 5300g firmwarebefore comboam4v2_1.2.0.b
- amd ryzen 3 5300ge firmwarebefore comboam4v2_1.2.0.b
- amd ryzen 3 5400u firmwarebefore cezannepi-fp6_1.0.0.fa
- amd ryzen 3 5425u firmwarebefore cezannepi-fp6_1.0.0.fa
- amd ryzen 3 7335u firmwarebefore rembrandtpi-fp7_1.0.0.9b
- amd ryzen 3 7440u firmwarebefore phoenixpi-fp8-fp7_1.0.0.2
- amd ryzen 5 5500h firmwarebefore cezannepi-fp6_1.0.0.fa
- amd ryzen 5 5560u firmwarebefore cezannepi-fp6_1.0.0.fa
- amd ryzen 5 5600g firmwarebefore comboam4v2_1.2.0.b
- amd ryzen 5 5600ge firmwarebefore comboam4v2_1.2.0.b
- amd ryzen 5 5600h firmwarebefore cezannepi-fp6_1.0.0.fa
- amd ryzen 5 5600hs firmwarebefore cezannepi-fp6_1.0.0.fa
- amd ryzen 5 5600u firmwarebefore cezannepi-fp6_1.0.0.fa
- amd ryzen 5 5625u firmwarebefore cezannepi-fp6_1.0.0.fa
- amd ryzen 5 6600h firmwarebefore rembrandtpi-fp7_1.0.0.9b
- amd ryzen 5 6600hs firmwarebefore rembrandtpi-fp7_1.0.0.9b
- amd ryzen 5 6600u firmwarebefore rembrandtpi-fp7_1.0.0.9b
- amd ryzen 5 7500f firmwarebefore comboam5pi_1.0.8.0
- amd ryzen 5 7535hs firmwarebefore rembrandtpi-fp7_1.0.0.9b
Versions reported by the vendor
Affected version ranges reported by the assigning authority (AMD). Independent of NVD's CPE analysis and usually ahead of it.
AMD AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics "Rembrandt"
- variousaffected
AMD AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics “Rembrandt-R”
- variousaffected
AMD Ryzen™ 5000 Series Desktop Processor with Radeon™ Graphics Formerly codenamed “Cezanne” AM4
- variousaffected
AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics “Cezanne”
- variousaffected
AMD Ryzen™ 7000 Series Desktop Processors with Radeon™ Graphics Formerly codenamed “Raphael”
- variousaffected
AMD Ryzen™ 7000 Series Desktop Processors with Radeon™ Graphics Formerly codenamed “Raphael” X3D
- variousaffected
AMD Ryzen™ 7040 Series Mobile Processors with Radeon™ Graphics Formerly codenamed “Phoenix”
- variousaffected
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-20559
Insufficient control flow management in AmdCpmGpioInitSmm may allow a privileged attacker to tamper with the SMM handler potentially lead35Monitor
- CVE-2023-20558
Insufficient control flow management in AmdCpmOemSmm may allow a privileged attacker to tamper with the SMM handler potentially leading to 35Monitor
- CVE-2021-26384A malformed SMI (System Management Interface) command may allow an attacker to establish a corrupted SMI Trigger Info data structure, potent31Monitor
- CVE-2023-20579Improper
Access Control in the AMD SPI protection feature may allow a user with Ring0
(kernel mode) privileged access to bypass protections 24Monitor
- CVE-2021-46758Insufficient validation of SPI flash addresses in the ASP (AMD Secure Processor) bootloader may allow an attacker to read data in memory map24Monitor
- CVE-2021-26382An attacker with root account privileges can load any legitimately signed firmware image into the Audio Co-Processor (ACP,) irrespective of 17Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.