CVE-2025-0037: AMD Platform Loader and Manager (PLM) · Improper Input Validation
Affects AMD Platform Loader and Manager (PLM)Source CVE Database V5
Not known to be exploited · CVSS 6.6 Medium.
Data as of 26 Oct 2026, 12:54 UTC
- 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:L/UI:N/S:U/C:L/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
AI-suggested
To mitigate CVE-2025-0037, European organizations should: 1) Monitor AMD's official security bulletins (AMD-SB-8010) for patches or firmware updates addressing this vulnerability and apply them promptly once available. 2) Implement strict access controls and network segmentation to limit local access to devices running the affected PLM firmware, reducing the risk of local exploitation. 3) Employ endpoint detection and response (EDR) solutions capable of detecting anomalous local activity indicative of attempts to exploit firmware vulnerabilities. 4) Harden device configurations by disabling unnecessary services or interfaces that could provide local access to untrusted users. 5) Conduct regular security audits and penetration testing focusing on firmware and low-level components to identify potential exploitation paths. 6) For critical deployments, consider hardware-based security features such as Trusted Platform Modules (TPMs) or secure boot mechanisms to detect unauthorized firmware modifications. 7) Establish incident response plans that include firmware compromise scenarios to ensure rapid containment and recovery. These measures go beyond generic advice by focusing on limiting local access, monitoring for exploitation attempts, and preparing for firmware-level incidents.
Description
In AMD Versal Adaptive SoC devices, the lack of address validation when executing PLM runtime services through the PLM firmware can allow access to isolated or protected memory spaces, resulting in the loss of integrity and confidentiality.