Skip to content
Noroxi
NVD / CVE Program· CNA AMD

CVE-2021-26353: Failure to validate inputs in SMM may allow an attacker to create a mishandled error leaving the DRTM UApp in a partially initialized state…

HighCVSS 7.8 · v3.1—No exploit No fix recorded

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
  • 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.
  • According to the record, no fixed version is available yet.

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Failure to validate inputs in SMM may allow an attacker to create a mishandled error leaving the DRTM UApp in a partially initialized state potentially resulting in loss of memory integrity.

Published
May 10, 2022
Updated
Jun 16, 2026
EPSS
0.2% · 19th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-26353

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for amd records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
amdepyc 7763 firmware
amdepyc 7763
amdepyc 7713p firmware
amdepyc 7713p
amdepyc 7713 firmware
amdepyc 7713
amdepyc 7663 firmware
amdepyc 7663
amdepyc 7643 firmware
amdepyc 7643
amdepyc 75f3 firmware
amdepyc 75f3

and 34 more

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 3rd Gen EPYC

    • variousaffected
Affected versions · NVD (20)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • amd epyc 72f3 firmwarebefore milanpi-sp3_1.0.0.4
  • 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 7373x firmwarebefore milanpi-sp3_1.0.0.4
  • amd epyc 73f3 firmwarebefore milanpi-sp3_1.0.0.4
  • amd epyc 7413 firmwarebefore milanpi-sp3_1.0.0.4
  • amd epyc 7443 firmwarebefore milanpi-sp3_1.0.0.4
  • amd epyc 7443p firmwarebefore milanpi-sp3_1.0.0.4
  • amd epyc 7453 firmwarebefore milanpi-sp3_1.0.0.4
  • amd epyc 7473x firmwarebefore milanpi-sp3_1.0.0.4
  • amd epyc 74f3 firmwarebefore milanpi-sp3_1.0.0.4
  • amd epyc 7513 firmwarebefore milanpi-sp3_1.0.0.4
  • amd epyc 7543 firmwarebefore milanpi-sp3_1.0.0.4
  • amd epyc 7543p firmwarebefore milanpi-sp3_1.0.0.4
  • amd epyc 7573x firmwarebefore milanpi-sp3_1.0.0.4
  • amd epyc 75f3 firmwarebefore milanpi-sp3_1.0.0.4
  • amd epyc 7643 firmwarebefore milanpi-sp3_1.0.0.4
  • amd epyc 7663 firmwarebefore milanpi-sp3_1.0.0.4
  • amd epyc 7713 firmwarebefore milanpi-sp3_1.0.0.4

Same product

amd: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-46771Insufficient validation of addresses in AMD Secure Processor (ASP) firmware system call may potentially lead to arbitrary code execution by…
    31Monitor
  • CVE-2021-26324A bug with the SEV-ES TMR may lead to a potential loss of memory integrity for SNP-active VMs.
    31Monitor
  • CVE-2023-20566Improper address validation in ASP with SNP enabled may potentially allow an attacker to compromise guest memory integrity.
    30Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2020-12966Feb 4, 2022 · AMD EPYC™ Processors contain an information disclosure vulnerability in the Secure Encrypted Virtualization with Encrypted State (SEV-ES)…
    22Monitor
  • ← EarlierCVE-2021-26332May 10, 2022 · Failure to verify SEV-ES TMR is not in MMIO space, SEV-ES FW could result in a potential loss of integrity or availability.
    28Monitor
  • Later →CVE-2021-26370May 10, 2022 · Improper validation of destination address in SVC_LOAD_FW_IMAGE_BY_INSTANCE and SVC_LOAD_BINARY_BY_ATTRIB in a malicious UApp or ABL may…
    28Monitor

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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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-665 · Improper Initialization

CVSS 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.

ATT&CK techniques

—

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records