cve.bz

CVE-2025-0038 amd

6.6 mediumEPSS 0.1%

Medium (6.6) in amd. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
In AMD Zynq UltraScale+ devices, the lack of address validation when executing CSU runtime services through the PMU Firmware can allow access to isolated or protected memory spaces resulting in the loss of integrity and confidentiality.

Severity

CVSS 3.1

6.6 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1284 Improper Validation of Specified Quantity in Input
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2025-0038 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-0038?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-0038?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-0038 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-0038

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-0038](https://cve.bz/cve/badge/CVE-2025-0038.svg)](https://cve.bz/cve/CVE-2025-0038)

HTML:

<a href="https://cve.bz/cve/CVE-2025-0038"><img src="https://cve.bz/cve/badge/CVE-2025-0038.svg" alt="CVE-2025-0038"></a>

Affected

  • amd:kria(tm) som
  • amd:zynq ultrascale+ mpsocs
  • amd:zynq ultrascale+ rfsocs

Versions

From the CNA's record in the CVE List.

ProductAffected
AMD Kria(TM) SOMPMU Firmware version TBD
AMD Zynq UltraScale+ MPSoCsPMU Firmware version TBD
AMD Zynq UltraScale+ RFSoCsPMU Firmware version TBD

References

Check your stackJSON