Security readout for executives and security teams
Plain-English summary
This is a high-severity AMD GPU security issue in the AMD Secure Processor. A local attacker with low privileges could potentially read or modify protected memory, which may lead to arbitrary code execution. Business urgency is highest for GPU workstations, engineering fleets, and ROCm/Instinct systems where untrusted local users or shared compute access exists.
Executive priority
Treat this as a high-priority endpoint and GPU-compute exposure issue, not a broad remote internet emergency. Prioritize assets where local users, contractors, developers, or shared compute workloads could reach affected AMD GPU software.
Technical view
CVE-2023-31317 is a CWE-119 memory bounds issue in the AMD Secure Processor affecting listed Radeon RX, Radeon PRO, and Instinct products. The CVSS 4.0 score is 8.8 with local attack vector, high complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impacts.
Likely exposure
Exposure is limited to systems running the affected AMD GPU products and versions listed in the CVE bundle: Radeon RX 6000/7000, Radeon PRO W6000/W7000, and Instinct MI210/MI250 with the named AMD Software or ROCm versions.
Exploitation context
The source bundle does not show CISA KEV listing or public active exploitation. The CVSS vector indicates exploitation requires local access, low privileges, and high attack complexity, reducing internet-wide risk but increasing concern on shared workstations, developer systems, and GPU compute hosts.
Researcher notes
Available evidence identifies product families, versions, CWE-119, CVSS 4.0 scoring, and potential protected-memory read/write leading to code execution. The bundle does not provide exploit details, proof of exploitation, or a specific named fixed version beyond referring to AMD-SB-6027.
Mitigation direction
- Review AMD bulletin AMD-SB-6027 for current vendor remediation guidance.
- Inventory systems with the affected AMD GPU product families.
- Compare installed AMD Software and ROCm versions against the affected list.
- Restrict unnecessary local user access on affected GPU hosts.
- Prioritize remediation for shared compute, engineering, and high-value workstation environments.
- Monitor CVE, AMD, and KEV sources for updated exploitation or fix information.
Validation and detection
- Confirm whether each host uses an affected AMD GPU product family.
- Record installed AMD Software or ROCm version on each in-scope system.
- Validate vendor guidance before declaring a system remediated.
- Check whether affected hosts allow untrusted or shared local user access.
- Document exceptions where updates are delayed pending AMD 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-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 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-31317 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.8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/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.
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:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——AMDVulnerability scoring details
Base CVSS 4.0 score
8.8HighVector: CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
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-6027.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.
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.