LiveActive security incident?Get immediate response
CVE Record

CVE-2021-26351: Insufficient DRAM address validation in System Management Unit (SMU) may result in a DMA (Direct Memory Acc...

Insufficient DRAM address validation in System Management Unit (SMU) may result in a DMA (Direct Memory Access) read/write from/to invalid DRAM address that could result in denial of service.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This AMD issue affects some Ryzen and Athlon systems. The System Management Unit may insufficiently validate DRAM addresses, allowing invalid DMA reads or writes that could crash or disrupt the system. The public bundle does not provide a CVSS score, fixed version, exploit prerequisites, or evidence of active exploitation.

Executive priority

Set priority after confirming asset exposure. This is potentially business-impacting because it can cause denial of service, but urgency is constrained by missing severity, exploitability, and remediation details in the provided sources.

Technical view

CVE-2021-26351 describes insufficient DRAM address validation in AMD SMU firmware or logic. The stated impact is DMA read/write access to invalid DRAM addresses, resulting in denial of service. The provided sources identify affected AMD Ryzen and Athlon Series as various versions, without model-level scope or remediation detail in the bundle.

Likely exposure

Exposure is limited to systems using affected AMD Ryzen or Athlon Series processors. Exact model, platform, and firmware exposure cannot be determined from the bundle alone; asset teams should map processor inventory against AMD bulletin SB-1027 and OEM platform guidance.

Exploitation context

The source bundle does not show CISA KEV listing, public exploitation, exploit maturity, required privileges, or attack vector. Treat active exploitation as unconfirmed. The described consequence is denial of service, not confirmed code execution or data theft.

Researcher notes

The bundle lacks CVSS, CWE, affected model granularity, prerequisites, and fix metadata. Analysis should stay anchored to AMD SB-1027 and CVE records. Do not infer broader AMD product impact or active exploitation without additional cited evidence.

Mitigation direction

  • Review AMD Security Bulletin SB-1027 for exact affected platforms and vendor guidance.
  • Check OEM BIOS, firmware, and platform advisories for applicable updates.
  • Apply supported vendor remediation where AMD or the OEM identifies it.
  • Prioritize systems where downtime would affect critical business services.
  • Monitor AMD and OEM advisories for updated scope or remediation details.

Validation and detection

  • Inventory systems using AMD Ryzen or Athlon processors.
  • Compare processor and platform details against AMD SB-1027.
  • Record current BIOS, firmware, and OEM support status for affected assets.
  • Confirm whether vendor guidance lists remediation for each platform.
  • Track unexplained instability or denial-of-service symptoms on exposed systems.
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-26351 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
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.