Security readout for executives and security teams
Plain-English summary
This vulnerability affects AMD power management firmware for specific AMD Instinct accelerators. A highly privileged local attacker could send malformed messages to the system management unit, potentially executing code. The business risk is concentrated in systems using AMD Instinct MI210 or MI250 with ROCm 6.4.2.
Executive priority
Treat as a targeted high-priority infrastructure risk, not a broad perimeter emergency. Focus on environments where affected AMD Instinct accelerators support sensitive AI, HPC, or shared workloads.
Technical view
CVE-2023-31313 is a CWE-441 unintended proxy/intermediary issue in AMD PMFW. The published CVSS is 7.2: local attack vector, high complexity, high privileges, no user interaction, changed scope, and high confidentiality and integrity impact with no availability impact.
Likely exposure
Exposure appears limited to AMD Instinct MI210 and MI250 deployments listed with ROCm 6.4.2. The provided sources do not identify broader AMD product families or other ROCm versions as affected.
Exploitation context
No provided source reports active exploitation, and the CVE is not marked as CISA KEV. Exploitation requires local access and high privileges, reducing broad internet risk but increasing concern for shared GPU, HPC, AI, or cloud environments.
Researcher notes
Evidence is limited to the CVE record and AMD bulletin reference. Do not assume exploitability beyond a privileged local attacker sending malformed PMFW-to-SMU messages. Patch specifics were not included in the provided source bundle.
Mitigation direction
- Review AMD-SB-6024 for vendor-provided update or mitigation guidance.
- Identify systems running AMD Instinct MI210 or MI250 with ROCm 6.4.2.
- Prioritize remediation for shared compute, multi-tenant, or high-trust workloads.
- Limit administrative access to affected accelerator hosts.
- Monitor AMD advisories for revised affected versions or firmware updates.
Validation and detection
- Confirm installed accelerator model and ROCm version on relevant hosts.
- Check whether AMD PMFW or ROCm updates from AMD have been applied.
- Verify privileged access paths to affected systems are restricted and logged.
- Review security monitoring for unusual privileged activity on accelerator hosts.
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-441: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-31313 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
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N
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.
SSVC decision data
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:C/C:H/I:H/A:N0.85.8AMDVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-6024.htmlCVE reference, AMD
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.
Unintended Proxy or Intermediary ('Confused Deputy')
Unintended Proxy or Intermediary ('Confused Deputy') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.