Skip to content
Fencer Vulns
low 3.2

CVE-2025-0036 json

In AMD Versal Adaptive SoC devices, the incorrect configuration of the SSS during runtime (post-boot) cryptographic operations could cause…

published 2025-06-09 16 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-17610

cvss
3.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 4%
public exploits
0
none known

Summary

In AMD Versal Adaptive SoC devices, the incorrect configuration of the SSS during runtime (post-boot) cryptographic operations could cause data to be incorrectly written to and read from invalid locations as well as returning incorrect cryptographic data.

Patch / fix

  • AMD Versal Adaptive SoC Devices 2025.1 release
  • AMD Versal RF Series 2025.1 release
  • AMD Versal AI Edge Series 2025.1 release
  • AMD Versal Prime Series 2025.1 release
  • AMD Versal Premium Series 2025.1 release
  • AMD Versal AI Core Series 2025.1 release
  • AMD Versal HBM Series 2025.1 release
  • AMD Alveo V80 Compute Accelerator 2025.1 release

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
16 mo ago

Exploit prediction

0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.2 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N

Affected products

  • AMD Versal Adaptive SoC Devices
  • AMD Versal RF Series
  • AMD Versal AI Edge Series
  • AMD Versal Prime Series
  • AMD Versal Premium Series
  • AMD Versal AI Core Series
  • AMD Versal HBM Series
  • AMD Alveo V80 Compute Accelerator

Classification

Weakness
  • CWE-682 Incorrect Calculation
  • CWE-772 Missing Release of Resource after Effective Lifetime
  • CWE-940 Improper Verification of Source of a Communication Channel
  • CWE-941 Incorrectly Specified Destination in a Communication Channel
  • CWE-497 Exposure of Sensitive System Information to an Unauthorized Control Sphere

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.