Security readout for executives and security teams
Plain-English summary
This is a firmware-level AMD platform issue in the secure execution environment. The practical risk is constrained because exploitation requires local access, high privileges, high complexity, and access to AMD signing keys. If achieved, it could crash affected systems and may expose limited confidentiality or integrity impact.
Executive priority
Handle through normal firmware patch governance with higher attention for critical servers and shared infrastructure. The business impact is mainly availability disruption, but the attack prerequisites make emergency response unnecessary based on the provided sources.
Technical view
AMD describes missing stack protection in ASP Secure OS TEE. A privileged attacker with AMD signing-key access could corrupt a return address through a stack-based buffer overrun, potentially causing denial of service. The CVSS 3.1 score is 5.2 with local attack vector, high complexity, and high privileges required.
Likely exposure
Exposure is most relevant for organizations running affected AMD EPYC, Ryzen, Threadripper, Athlon, and mobile processor platforms listed in AMD SB-3003 or the CVE record. Risk is tied to platform firmware/TEE exposure rather than an ordinary application package.
Exploitation context
The source bundle does not show active exploitation, and KEV status is false. The exploit preconditions are unusually restrictive: local access, high privileges, high complexity, and AMD signing-key access. Treat this as a firmware hygiene and resilience issue, not an internet-scale emergency.
Researcher notes
Evidence is limited to the CVE data and AMD advisory reference. The bundle names CWE-120 and describes return-address corruption in ASP Secure OS TEE, but it does not provide proof-of-concept status, detailed root cause, or exact fixed firmware mappings beyond affected product/version entries.
Mitigation direction
- Check AMD SB-3003 and OEM firmware advisories for your exact platform.
- Inventory systems using affected AMD EPYC, Ryzen, Threadripper, Athlon, and mobile processors.
- Prioritize BIOS or firmware updates where AMD or the OEM provides them.
- Restrict administrative access on affected hosts until firmware status is confirmed.
- Monitor AMD and OEM advisories for revised affected-version or remediation guidance.
Validation and detection
- Map hardware inventory to the affected product families in the CVE record.
- Record current BIOS, AGESA, or platform firmware versions for each affected system.
- Compare firmware versions against AMD SB-3003 and OEM release notes.
- Confirm whether listed Athlon desktop variants are marked unaffected before prioritizing them.
- Track remediation exceptions for systems without available OEM firmware guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-120: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-46746 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H0.54.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.2MediumVector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3003.htmlCVE reference · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.