LiveActive security incident?Get immediate response
CVE Record

CVE-2021-26373: Insufficient bound checks in the System Management Unit (SMU) may result in a system voltage malfunction th...

Insufficient bound checks in the System Management Unit (SMU) may result in a system voltage malfunction that could result in denial of resources and/or possibly denial of service.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE describes a flaw in AMD processor management logic that could cause voltage-related malfunction and interrupt system resources or service. The available bundle points to availability impact, not data theft. AMD EPYC, Ryzen, and Athlon families are listed broadly, so exact exposure needs model and firmware confirmation.

Executive priority

Handle as an availability-risk firmware issue. Give priority to AMD-based servers and critical workstations, but avoid emergency claims because the provided evidence lacks CVSS scoring, exploit details, KEV listing, and precise affected-version data.

Technical view

CVE-2021-26373 is an insufficient bounds-checking issue in AMD's System Management Unit. The described outcome is a system voltage malfunction that may cause denial of resources or denial of service. The bundle does not provide CVSS, CWE, exploit prerequisites, affected model granularity, or specific remediation text.

Likely exposure

Potential exposure exists where AMD EPYC, Ryzen, or Athlon processors from the referenced advisories are deployed. The source bundle says versions are various and does not identify exact models, firmware levels, operating systems, or cloud/provider scope.

Exploitation context

No active exploitation is supported by the provided sources, and the bundle marks KEV as false. The public description only states possible denial of resources or denial of service; it does not document exploit maturity, access requirements, or public weaponization.

Researcher notes

The record is sparse. It identifies an SMU bounds-checking weakness and broad AMD processor families, but not the vulnerable code path, attacker position, privilege requirement, model matrix, or fixed firmware versions. Research should stay anchored to AMD SB-1027, SB-1028, and OEM advisories.

Mitigation direction

  • Review AMD SB-1027 and SB-1028 for affected processor and firmware guidance.
  • Check OEM server, desktop, and laptop BIOS advisories for matching AMD platforms.
  • Prioritize systems supporting critical workloads or shared infrastructure.
  • Apply vendor-provided firmware or BIOS updates when confirmed applicable.
  • Track remediation exceptions where updates are unavailable or operationally risky.

Validation and detection

  • Inventory AMD EPYC, Ryzen, and Athlon assets by exact model and firmware version.
  • Compare each system against AMD and OEM advisory applicability.
  • Confirm whether firmware or BIOS updates have been installed successfully.
  • Monitor critical AMD systems for unexplained instability or service interruption.
  • Record unresolved systems for risk acceptance or maintenance scheduling.
Prepared
Confidence
medium
Sources
4

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-26373 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
3Source links

CVSS and timeline data

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

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AMDEPYC™ ProcessorsvariousListed
AMDRyzen™ SeriesvariousListed
AMDAthlon™ SeriesvariousListed
Weakness

CWE details

No CWE listed

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