Security readout for executives and security teams
Plain-English summary
CVE-2023-31324 affects AMD Secure Processor handling of certain GPU-related trusted-agent commands. A local, low-privileged attacker could race command processing and alter commands, potentially impacting confidentiality, integrity, or availability. This is most relevant to systems using listed AMD Radeon, Radeon PRO, and Instinct GPUs, especially shared workstations, compute nodes, and AI/HPC environments.
Executive priority
Treat as high priority for GPU-heavy or shared compute environments. The vulnerability requires local access and is not reported as actively exploited, but it affects trusted security processing and could undermine data integrity or confidentiality on valuable compute assets.
Technical view
The issue is a CWE-367 TOCTOU race condition in the AMD Secure Processor involving External Global Memory Interconnect Trusted Agent (XGMI TA) commands. AMD rates it high severity with CVSS 4.0 score 7.1. Attack prerequisites are local access, low privileges, high complexity, and no user interaction, with potential cross-security-scope impact.
Likely exposure
Exposure is limited to environments with the listed AMD GPU products and software stacks: Radeon RX 5000, Radeon PRO W5000, and Instinct MI210/MI250/MI300A/MI300X with the specified AMD Software or ROCm versions in the source bundle.
Exploitation context
No CISA KEV listing or provided source indicates active exploitation. The CVSS vector indicates exploitation requires local access and low privileges, but high attack complexity. Risk is higher on multi-user GPU servers, shared research clusters, virtualization hosts, and cloud-like compute environments.
Researcher notes
Evidence is limited to the CVE record and AMD bulletin reference. The source bundle names affected products and versions but does not provide exploit details or explicit fixed versions. Avoid assuming remote exposure. Focus validation on local privilege boundaries, GPU inventory, and official AMD remediation tracking.
Mitigation direction
- Review AMD bulletin AMD-SB-6024 for official remediation guidance.
- Inventory systems using the affected AMD GPU models and software versions.
- Prioritize shared GPU compute systems over single-user endpoints.
- Restrict local access to affected systems until vendor guidance is applied.
- Monitor AMD advisories for updated fixed-version information.
Validation and detection
- Check installed GPU model against AMD’s affected product list.
- Record AMD Software: Adrenalin, PRO Edition, or ROCm version.
- Confirm whether systems use shared local user access.
- Verify remediation status against AMD-SB-6024.
- Document exceptions where vendor guidance is not yet available.
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-367: 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-31324 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.1 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L
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:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
7.1HighVector: CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L
Source materials
- CVE List V5 sourceCVE List V5
- https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-6024.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.
Time-of-check Time-of-use (TOCTOU) Race Condition
Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.