Security readout for executives and security teams
Plain-English summary
CVE-2023-31364 is a denial-of-service issue in AMD systems where a malicious guest virtual machine can overwhelm the host through IOMMU-related memory writes. The stated impact is a fatal machine check error, potentially crashing the host. This matters most for virtualization platforms running untrusted or multi-tenant workloads.
Executive priority
Treat as high priority for cloud, hosting, lab, and enterprise virtualization environments using affected AMD processors. The business risk is host outage caused from inside a VM, not data theft. Patch planning depends on AMD/OEM firmware availability and is complicated for products marked “No Fix Planned.”
Technical view
AMD describes improper handling of direct memory writes in the input-output memory management unit. A malicious guest VM may flood the host with writes, causing a fatal machine check error. CVSS v4.0 is 8.3 high, with high availability impact to both vulnerable and subsequent systems, and no stated confidentiality or integrity impact.
Likely exposure
Exposure is most relevant on affected AMD EPYC and listed Ryzen/Athlon platforms used for virtualization, especially where guests are not fully trusted. AMD lists multiple EPYC server and embedded families as affected, and several Ryzen/Athlon families with “No Fix Planned.” Embedded EPYC 8004 and 9004 entries are listed as unaffected in the provided data.
Exploitation context
The source states exploitation requires a malicious guest VM. CVSS indicates low attack complexity, low privileges, no user interaction, and network attack vector. No provided source or KEV status indicates active exploitation in the wild.
Researcher notes
The public description is concise and does not include exploit details. AMD’s advisory is the key source for affected product mapping. The provided data names AMD PI versions and “No Fix Planned” statuses but does not provide universal fixed-version guidance in the bundle.
Mitigation direction
- Review AMD Security Bulletin AMD-SB-7059 for product-specific guidance.
- Check OEM BIOS or firmware updates for affected AMD platforms.
- Prioritize remediation for hosts running untrusted or multi-tenant VMs.
- For “No Fix Planned” products, seek AMD/OEM guidance and assess workload placement risk.
- Consider moving untrusted guests away from unremediated affected hosts.
Validation and detection
- Inventory AMD processor models used in virtualization hosts.
- Map each system to AMD-SB-7059 affected and unaffected entries.
- Check BIOS, firmware, or platform initialization versions against OEM guidance.
- Identify hosts running untrusted guest VMs or multi-tenant workloads.
- Review host logs for fatal machine check errors or unexplained crashes.
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-119: 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-2023-31364 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
- 8.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA: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:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.3HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7059.htmlCVE reference
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.
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.