AMD System Management Unit (SMU) contains a potential issue where a malicious user may be able to manipulate mailbox entries leading to arbi
AMD System Management Unit (SMU) contains a potential issue where a malicious user may be able to manipulate mailbox entries leading to arbitrary code execution.
- Published
- Nov 16, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 20th percentile
- CWE
- CWE-20
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| amd | epyc 7003 firmware | cpe:2.3:o:amd:epyc_7003_firmware |
| amd | epyc 7003 | cpe:2.3:h:amd:epyc_7003 |
| amd | epyc 7002 firmware | cpe:2.3:o:amd:epyc_7002_firmware |
| amd | epyc 7002 | cpe:2.3:h:amd:epyc_7002 |
| amd | epyc 7001 firmware | cpe:2.3:o:amd:epyc_7001_firmware |
| amd | epyc 7001 | cpe:2.3:h:amd:epyc_7001 |
| amd | epyc 72f3 firmware | cpe:2.3:o:amd:epyc_72f3_firmware |
| amd | epyc 72f3 | cpe:2.3:h:amd:epyc_72f3 |
| amd | epyc 7313 firmware | cpe:2.3:o:amd:epyc_7313_firmware |
| amd | epyc 7313 | cpe:2.3:h:amd:epyc_7313 |
| amd | epyc 7313p firmware | cpe:2.3:o:amd:epyc_7313p_firmware |
| amd | epyc 7313p | cpe:2.3:h:amd:epyc_7313p |
and 104 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amd epyc 7001 firmwarebefore naplespi-sp3_1.0.0.g
- amd epyc 7002 firmwarebefore romepi-sp3_1.0.0.c
- amd epyc 7003 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7232p firmwarebefore romepi-sp3_1.0.0.c
- amd epyc 7251 firmwarebefore naplespi-sp3_1.0.0.g
- amd epyc 7252 firmwarebefore romepi-sp3_1.0.0.c
- amd epyc 7262 firmwarebefore romepi-sp3_1.0.0.c
- amd epyc 7272 firmwarebefore romepi-sp3_1.0.0.c
- amd epyc 7281 firmwarebefore naplespi-sp3_1.0.0.g
- amd epyc 7282 firmwarebefore romepi-sp3_1.0.0.c
- amd epyc 72f3 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7301 firmwarebefore naplespi-sp3_1.0.0.g
- amd epyc 7302 firmwarebefore romepi-sp3_1.0.0.c
- amd epyc 7302p firmwarebefore romepi-sp3_1.0.0.c
- amd epyc 7313 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7313p firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7343 firmwarebefore milanpi-sp3_1.0.0.4
- amd epyc 7351 firmwarebefore naplespi-sp3_1.0.0.g
- amd epyc 7351p firmwarebefore naplespi-sp3_1.0.0.g
- amd epyc 7352 firmwarebefore romepi-sp3_1.0.0.c
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 1st Gen AMD EPYC™
- unspecified and later · before NaplesPI-SP3_1.0.0.Gaffected
AMD 2nd Gen AMD EPYC™
- unspecified and later · before RomePI-SP3_1.0.0.Caffected
AMD 3rd Gen AMD EPYC™
- unspecified and later · before MilanPI-SP3_1.0.0.4affected
Same product
amd: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-26335Improper input and range checking in the AMD Secure Processor (ASP) boot loader image header may allow an attacker to use attacker-controlle31Monitor
- CVE-2021-26315When the AMD Platform Security Processor (PSP) boot rom loads, authenticates, and subsequently decrypts an encrypted FW, due to insufficient31Monitor
- CVE-2020-12961A potential vulnerability exists in AMD Platform Security Processor (PSP) that may allow an attacker to zero any privileged register on the 31Monitor
- CVE-2023-20530Insufficient input validation of BIOS mailbox messages in SMU may result in out-of-bounds memory reads potentially resulting in a denial of 30Monitor
- CVE-2020-12951Race condition in ASP firmware could allow less privileged x86 code to perform ASP SMM (System Management Mode) operations.28Monitor
- CVE-2021-26404Improper input validation and bounds checking in SEV firmware may leak scratch buffer bytes leading to potential information disclosure.22Monitor
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
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- 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
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/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.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
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.