Security readout for executives and security teams
Plain-English summary
A flaw in AMD Radeon PRO V710 GPU isolation could let an attacker inside a malicious virtual machine disrupt the host. The documented impact is host reboot, creating denial of service. This is not described as data theft or code execution in the supplied sources.
Executive priority
Treat this as a focused availability risk, not a broad enterprise compromise. Prioritize cloud, VDI, AI, rendering, or multi-tenant virtualization environments using Radeon PRO V710, because a guest-side attacker could disrupt host availability.
Technical view
CVE-2024-36332 is CWE-1189 involving improper isolation of GPU hardware register space. A privileged attacker in a guest VM may gain unauthorized access to a victim range of GPU MMIO registers, potentially rebooting the host OS. CVSS v4.0 is 6.8 with local access, low privileges, no user interaction, and high availability impact.
Likely exposure
Exposure appears limited to environments using AMD Radeon PRO V710, especially where guest VMs receive GPU access. Fleets without this GPU, or without VM GPU assignment, are less likely affected based on the supplied sources.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The described attacker position is inside a malicious guest VM with privileges, making this most relevant to virtualized, multi-tenant, or less-trusted VM environments.
Researcher notes
Evidence is narrow but clear on impact and attacker position. The bundle names AMD Radeon PRO V710 and says affected versions require AMD Customer Engineering. Do not assume other AMD GPUs, exploit availability, or a specific patch without vendor confirmation.
Mitigation direction
- Review AMD bulletin AMD-SB-6027 for current vendor guidance.
- Contact AMD Customer Engineering for affected version and remediation details.
- Restrict Radeon PRO V710 access to trusted guest VMs where feasible.
- Separate untrusted tenants from hosts using affected GPU virtualization.
- Monitor affected hosts for unexpected reboots or GPU-related faults.
Validation and detection
- Inventory hosts using AMD Radeon PRO V710 GPUs.
- Identify which VMs receive direct or virtualized GPU access.
- Confirm whether untrusted or external tenants can use those VMs.
- Check AMD guidance for exact affected configurations and updates.
- Review incident logs for unexplained host reboots in GPU-enabled clusters.
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-1189: 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-2024-36332 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
- 6.8 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA: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:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N——AMDVulnerability scoring details
Base CVSS 4.0 score
6.8MediumVector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA: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-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 Isolation of Shared Resources on System-on-a-Chip (SoC)
Improper Isolation of Shared Resources on System-on-a-Chip (SoC) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.