LiveActive security incident?Get immediate response
CVE Record

CVE-2021-26364: Insufficient bounds checking in an SMU mailbox register could allow an attacker to potentially read outside...

Insufficient bounds checking in an SMU mailbox register could allow an attacker to potentially read outside of the SRAM address range which could result in an exception handling leading to a potential denial of service.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-26364 is an AMD EPYC processor firmware issue. A bounds-checking weakness in an SMU mailbox register could let an attacker trigger an out-of-range SRAM read, potentially causing exception handling and denial of service. The public bundle does not provide a CVSS score or confirm exploitation.

Executive priority

Handle as a medium-priority availability risk until platform-specific guidance confirms exposure. Prioritize critical EPYC servers, virtualization hosts, and systems with strict uptime requirements, but avoid emergency assumptions because public evidence does not show known exploitation.

Technical view

The issue is insufficient bounds checking in an SMU mailbox register on various AMD EPYC processors. The described impact is a potential read outside the SRAM address range, leading to exception handling and possible denial of service. Available sources do not describe prerequisites, privilege level, affected generations, or a specific remediation.

Likely exposure

Exposure is limited to environments running affected AMD EPYC processors. The bundle says versions are various, but does not identify exact models, firmware versions, operating systems, cloud instance types, or appliance vendors.

Exploitation context

The provided sources do not indicate active exploitation, and the CVE is not listed as KEV in the bundle. No exploit details, attack path, or required access level are provided, so real-world exploitability cannot be determined from this evidence alone.

Researcher notes

Key missing details are exact affected EPYC generations, firmware ranges, attacker prerequisites, and patch identifiers. Analysis should stay anchored to AMD SB-1028 and OEM platform advisories rather than assuming a universal software-only fix.

Mitigation direction

  • Review AMD SB-1028 for model-specific guidance and updates.
  • Check server OEM advisories for BIOS or firmware updates.
  • Prioritize availability-critical EPYC hosts for assessment.
  • Track vendor guidance if exact affected versions are unclear.

Validation and detection

  • Inventory systems using AMD EPYC processors.
  • Map processor models against AMD SB-1028 and OEM guidance.
  • Record current BIOS, firmware, and platform update levels.
  • Review monitoring for unexplained host exceptions or reboots.
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.

cve · low confidence lookup

CVE-2021-26364 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AMDEPYC™ ProcessorsvariousListed
Weakness

CWE details

No CWE listed

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