cve.bz

CVE-2025-54507 amd

5.9 mediumEPSS 0.2%

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

On this page
Improper validation of consistency within input in AMD SEV (Secure Encrypted Virtualization) firmware could allow an attacker with administrative privileges to create multiple RMP entries for the same guest physical address, potentially resulting in loss of guest integrity.

Severity

CVSS 4.0

5.9 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-13. 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 2026-11-13. 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-1288 Improper Validation of Consistency within Input
Published
Modified
Assigned by
AMD (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2025-54507 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-54507?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-54507?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-54507 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-54507

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-54507](https://cve.bz/cve/badge/CVE-2025-54507.svg)](https://cve.bz/cve/CVE-2025-54507)

HTML:

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

Affected

  • amd:amd epyc™ 9005 series processors
  • amd:amd epyc™ embedded 9005 series processors

References

Check your stackJSON