Is CVE-2023-31316 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2023-31316 being exploited in the wild.

How severe is CVE-2023-31316?

Informational severity, with a CVSS score of 7.1, published 15 May 2026.

Which products and versions are affected?

AMD Secure Processor (ASP); AMD Video Core Next (VCN) firmware.

Is there a fix for CVE-2023-31316?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2023-31316 attacked?

It is attacked with local access, in device firmware.

Am I affected by CVE-2023-31316?

Check whether you run Amd Secure Processor or Amd Video Core Next. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2023-31316: AMD Secure Processor integrity loss during power save/restore

CVE-2023-31316 · Severity: info · CVSS 7.1 · Published 2026-05-15

A vulnerability in the AMD Secure Processor could allow an attacker to interfere with how the system handles power-saving transitions. By exploiting this flaw, a local user with specific access could manipulate the video processing firmware, potentially leading to unauthorized access to data or system instability. This impacts the fundamental security layer designed to protect sensitive hardware configurations during sleep or low-power modes.

Technologies: Amd Secure Processor. Vendors: Amd.

Quick answers

Is CVE-2023-31316 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2023-31316 being exploited in the wild.
How severe is CVE-2023-31316?: Informational severity, with a CVSS score of 7.1, published 15 May 2026.
Which products and versions are affected?: AMD Secure Processor (ASP); AMD Video Core Next (VCN) firmware.
Is there a fix for CVE-2023-31316?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2023-31316 attacked?: It is attacked with local access, in device firmware.
Am I affected by CVE-2023-31316?: Check whether you run Amd Secure Processor or Amd Video Core Next. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is classified as CWE-1304, involving the improper preservation of hardware configuration state integrity during power save/restore cycles within the AMD Secure Processor (ASP). An attacker who already possesses the capability to write outside the Trusted Memory Range (TMR) can exploit this state-handling flaw to redirect or modify the execution flow of the Video Core Next (VCN) firmware. This is a local attack requiring low privileges but high complexity and specific preconditions. Successful exploitation could compromise the confidentiality and integrity of the secure environment. AMD has addressed this in security bulletins AMD-SB-4017 and AMD-SB-6027.

Affected products

AMD Secure Processor (ASP)
AMD Video Core Next (VCN) firmware

Timeline

2026-05-15: advisory: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.