LiveActive security incident?Get immediate response
CVE Record

CVE-2021-26379: Insufficient input validation of mailbox data in the SMU may allow an attacker to coerce the SMU to corrupt...

Insufficient input validation of mailbox data in the SMU may allow an attacker to coerce the SMU to corrupt SMRAM, potentially leading to a loss of integrity and privilege escalation.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This is an AMD server firmware vulnerability affecting some 2nd and 3rd Gen EPYC platforms. Badly validated SMU mailbox data could corrupt protected SMRAM memory, which may let an attacker gain higher privileges or undermine system integrity.

Executive priority

Treat as a high-priority firmware governance issue for AMD EPYC server fleets. Prioritize asset identification and vendor firmware updates, especially for critical infrastructure and sensitive workloads. Urgency is driven by severity, not confirmed exploitation.

Technical view

CVE-2021-26379 involves insufficient input validation of mailbox data in AMD's System Management Unit. The reported impact is SMRAM corruption with potential integrity loss and privilege escalation. The source bundle identifies AMD AGESA for 2nd and 3rd Gen EPYC as affected in various versions.

Likely exposure

Exposure is most likely on servers using affected AMD EPYC 2nd or 3rd Gen platforms with vulnerable AGESA-based BIOS or firmware. Exact affected and fixed versions are not provided in the bundle.

Exploitation context

The CVE has a CVSS 3.1 score of 9.8 and is marked critical. The bundle does not cite CISA KEV listing or any active exploitation evidence. No public exploit details are included.

Researcher notes

The public description is concise and does not include root-cause detail, exploitability constraints, or fixed AGESA versions. Validation should remain inventory- and advisory-driven rather than exploit-driven. Avoid assuming exposure beyond listed AMD EPYC generations and AGESA firmware context.

Mitigation direction

  • Review AMD-SB-3001 and relevant server OEM firmware advisories.
  • Apply vendor-provided BIOS or AGESA firmware updates where available.
  • Prioritize production EPYC hosts that process sensitive workloads.
  • Track exceptions where firmware cannot be updated promptly.

Validation and detection

  • Inventory systems with 2nd and 3rd Gen AMD EPYC processors.
  • Record current BIOS, firmware, and AGESA versions from asset data.
  • Compare platform firmware against AMD and OEM advisory guidance.
  • Confirm remediation through change records and post-update firmware version checks.
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.

description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-26379 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2021-26379Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
AMD2nd Gen AMD EPYC™AGESA, variousunaffected
AMD3rd Gen AMD EPYC™AGESA, variousunaffected
Weakness

CWE details

No CWE listed

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