Quick answers
- Is CVE-2025-62620 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-62620 being exploited in the wild.
- How severe is CVE-2025-62620?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Amd EPYC <UNKNOWN>.
- Is there a fix for CVE-2025-62620?
- 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-62620 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2025-62620?
- Check whether you run Amd EPYC at an affected version. 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 vulnerability exists in the ring buffer queue status page handling due to improper validation of unsafe equivalence in input. An attacker with high privilege level (guest-level access) can exploit this to reclaim the queue status page, leading to potential loss of guest memory integrity in shared virtualization scenarios. This is a logic flaw in input validation rather than a memory safety issue.
Affected products
- AMD EPYC <UNKNOWN>
Timeline
- 2026-11-10: disclosed