LiveActive security incident?Get immediate response
CVE Record

CVE-2021-26404: Improper input validation and bounds checking in SEV firmware may leak scratch buffer bytes leading to pote...

Improper input validation and bounds checking in SEV firmware may leak scratch buffer bytes leading to potential information disclosure.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This AMD SEV firmware flaw could expose sensitive memory contents from an internal scratch buffer. It is not described as remotely exploitable, but it matters for organizations relying on AMD EPYC-based virtualization security because confidentiality is the affected outcome.

Executive priority

Treat this as a targeted confidentiality risk for EPYC virtualization environments. It is not flagged as actively exploited in the provided sources, but systems protecting sensitive workloads with SEV should be checked and updated through vendor-supported firmware channels.

Technical view

CVE-2021-26404 is improper input validation and bounds checking in AMD SEV firmware. The CVSS vector is local, low complexity, low privileges, no user interaction, with high confidentiality impact and no integrity or availability impact.

Likely exposure

Exposure is most likely on systems using AMD 3rd Gen EPYC platforms and affected AGESA or SEV firmware versions. The source bundle lists versions only as various, so exact exposure requires vendor or OEM mapping.

Exploitation context

The bundle does not show CISA KEV listing, active exploitation, or public exploit evidence. The CVSS vector indicates local access with low privileges is required. Impact is potential information disclosure, not takeover or service disruption.

Researcher notes

The public bundle gives the weakness class, impact, CVSS vector, affected product family, and AMD advisory link, but not exact affected firmware builds or fixed versions. Avoid broader product assumptions unless confirmed by AMD or OEM documentation.

Mitigation direction

  • Review AMD-SB-1032 for affected platform and firmware guidance.
  • Ask server OEMs for BIOS or AGESA update applicability.
  • Prioritize hosts using AMD SEV for sensitive virtualization workloads.
  • Track remediation through normal firmware change-control windows.
  • If no update is available, follow vendor compensating guidance.

Validation and detection

  • Inventory AMD 3rd Gen EPYC systems and firmware levels.
  • Identify which hosts have SEV enabled or depended upon.
  • Compare BIOS, AGESA, and SEV firmware against AMD guidance.
  • Confirm whether cloud or hosting providers manage firmware remediation.
  • Record systems where affected-version evidence remains incomplete.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-26404 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2021-26404Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AMD3rd Gen EPYCAGESA, variousunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.