LiveActive security incident?Get immediate response
CVE Record

CVE-2021-46762: Insufficient input validation in the SMU may allow an attacker to corrupt SMU SRAM potentially leading to a...

Insufficient input validation in the SMU may allow an attacker to corrupt SMU SRAM potentially leading to a loss of integrity or denial of service.

LowCVSS 3.9Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a low-severity AMD server processor firmware issue. A highly privileged local attacker may be able to corrupt SRAM used by the System Management Unit, potentially causing limited integrity impact or denial of service. It is not described as remotely exploitable or actively exploited in the supplied sources.

Executive priority

Treat this as routine firmware risk management, not an emergency. Prioritize confirmation and scheduled remediation for critical AMD EPYC infrastructure, especially where local administrative access is broadly shared or difficult to control.

Technical view

CVE-2021-46762 is insufficient input validation in the AMD SMU affecting listed EPYC and EPYC Embedded platforms using AGESA. The CVSS vector requires local access, high attack complexity, and high privileges, with no user interaction and no confidentiality impact. Potential outcomes are SMU SRAM corruption, limited integrity loss, or availability impact.

Likely exposure

Exposure is most relevant to organizations running 2nd or 3rd Gen AMD EPYC, EPYC Embedded 7002, or EPYC Embedded 7003 systems with affected AGESA firmware. The supplied data says affected versions are “various,” so exact exposure requires checking AMD and OEM firmware guidance.

Exploitation context

The bundle does not show CISA KEV status or any cited active exploitation. The CVSS vector indicates an attacker needs local, highly privileged access and high attack complexity, making this more relevant after compromise or in tightly controlled administrative contexts than as an initial intrusion path.

Researcher notes

Evidence is limited to the CVE record and AMD advisories. The bundle does not provide CWE classification, exact fixed versions, exploit details, or active exploitation. Avoid broad product claims; validate AGESA and OEM firmware applicability before assigning exposure.

Mitigation direction

  • Review AMD-SB-3001 and AMD-SB-5001 for affected AGESA and platform guidance.
  • Check server OEM BIOS or firmware advisories for the same AMD bulletin mapping.
  • Apply vendor-approved BIOS or firmware updates when your platform is listed as affected.
  • Prioritize systems where untrusted users or workloads can obtain privileged local access.

Validation and detection

  • Inventory AMD EPYC and EPYC Embedded systems in production and lab environments.
  • Record current BIOS, firmware, and AGESA versions from vendor management tools.
  • Compare platform firmware versions against AMD and OEM advisory guidance.
  • Confirm no unsupported assumptions that all EPYC systems are affected.
  • After remediation, verify firmware versions changed to vendor-recommended levels.
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-46762 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
Low
CVSS
3.9 (3.1)
Known Exploited
No
Published

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

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
3Source 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
3.9CVSS 3.1LowCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:N/I:L/A:L0.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.9Low
CVSS 3.1 vector shape for CVE-2021-46762Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
AMD2nd Gen AMD EPYC™AGESA, variousunaffected
AMD3rd Gen AMD EPYC™AGESA, variousunaffected
AMDAMD EPYC™ Embedded 7002variousunaffected
AMDAMD EPYC™ Embedded 7003variousunaffected
Weakness

CWE details

No CWE listed

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