CVE-2025-54503: AMD SEV firmware improper handling of memory range overlaps

CVE-2025-54503 · Severity: info · Published 2026-11-10

AMD's Secure Encrypted Virtualization (SEV) firmware handles memory protection incorrectly when address ranges overlap. A privileged attacker could exploit this misconfiguration to undermine the memory integrity guarantees that SEV is designed to provide, potentially exposing or modifying sensitive data in virtualized environments.

Technologies: Amd SEV firmware. Vendors: Amd.

Quick answers

Is CVE-2025-54503 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-54503 being exploited in the wild.
How severe is CVE-2025-54503?
Informational severity, published 10 November 2026.
Which products and versions are affected?
AMD SEV firmware.
Is there a fix for CVE-2025-54503?
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-2025-54503 attacked?
It is attacked with local access, in device firmware.
Am I affected by CVE-2025-54503?
Check whether you run Amd SEV firmware. 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 SEV firmware does not properly validate or reconcile overlapping protected memory ranges in the Reverse Map Table (RMP), allowing a privileged attacker to create conflicting RMP configurations. This results in memory regions that should be protected being left accessible or unencrypted, compromising the isolation guarantees between the host and encrypted virtual machines.

Affected products

  • AMD SEV firmware

Timeline

  • 2026-11-10: disclosed

References

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