Skip to main content
VulnerabilityPublished

CVE-2025-48508: AMD Radeon™ PRO V710 · Improper Finite State Machines (FSMs) in Hardware Logic

Affects AMD Radeon™ PRO V710Source CVE Database V5

0

Not known to be exploited · CVSS 6.0 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
AMDAMD Radeon™ PRO V710Affected–Fixed in–

AI-suggested

  1. Apply official AMD firmware or microcode updates addressing this vulnerability as soon as they become available.
  2. Restrict and monitor privileged access within guest virtual machines to minimize the risk of malicious actors gaining the necessary privileges to exploit the vulnerability.
  3. Implement strict access controls and auditing on virtualization hosts to detect unusual GPU reset or crash events.
  4. Consider isolating critical workloads from virtual machines that require GPU passthrough or sharing until patches are applied.
  5. Employ hypervisor-level security features to limit the impact of guest VM compromises on host hardware.
  6. Regularly update virtualization software and drivers to the latest versions to ensure compatibility with hardware fixes.
  7. Conduct thorough security assessments of virtualized environments to identify potential privilege escalation paths.
  8. Develop incident response plans that include GPU-related denial of service scenarios to minimize downtime.
  9. Engage with AMD support channels for guidance and early access to patches or mitigations.
  10. Monitor security advisories for updates on exploit developments or additional mitigations.

Description

Improper Hardware reset flow logic in the GPU GFX Hardware IP block could allow a privileged attacker in a guest virtual machine to control reset operation potentially causing host or GPU crash or reset resulting in denial of service.

References

Community reviews

Loading reviews…