CVE-2025-52535VulnerabilityPublished 11 Nov 2026

Improper Resource Reuse

Source GCVE Database

Compare

Authoritative record:CVE-2025-52535· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium.

Data as of 11 Nov 2026, 01:50 UTC

CVSS 4.0 base score

5.9Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (AMD)	CVSS 4.0	5.9

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

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: High
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the Subsequent System. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the Subsequent System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-cj53-4h86-p2r9

What to do

Affected software

Product	Affected	Fixed in
AMDAMD EPYC™ 9004 Series Processors	Affected–	Fixed in–
AMDAMD EPYC™ 7003 Series Processors	Affected–	Fixed in–
AMDAMD EPYC™ 9005 Series Processors	Affected–	Fixed in–
AMDAMD EPYC™ 8004 Series Processors	Affected–	Fixed in–
AMDAMD EPYC™ Embedded 7003 Series Processors	Affected–	Fixed in–
AMDAMD EPYC™ Embedded 9004 Series Processors (formerly codenamed "Genoa")	Affected–	Fixed in–

AI-suggested

In the meantime, limit hypervisor access to trusted administrators and environments to reduce risk.

Description

CVE-2025-52535 is a vulnerability in the AMD Secure Encrypted Virtualization (SEV) firmware involving improper resource reuse. An attacker with hypervisor-level access could exploit this flaw to write to the Reverse Map Table (RMP) protected memory. This may lead to a loss of guest memory integrity, potentially compromising the isolation guarantees of SEV. The vulnerability has a medium severity rating with a CVSS score of 5.9. No patch or remediation information is currently available.

Impact

An attacker with hypervisor privileges could write to memory regions protected by the Reverse Map Table, potentially causing loss of guest memory integrity. This undermines the security guarantees of AMD SEV, which is designed to protect virtual machine memory confidentiality and integrity from a compromised hypervisor. However, exploitation requires already having high-level hypervisor access, limiting the attack surface.

Summary

This vulnerability arises from improper resource reuse in the AMD SEV firmware, allowing an attacker who already has hypervisor access to write to RMP-protected memory regions. The Reverse Map Table is critical for maintaining memory integrity and isolation in SEV environments. Exploitation could undermine guest memory integrity, weakening the security model of SEV. The CVSS 4.0 vector indicates local attack vector with low complexity and no user interaction required, but high privileges are needed. No known exploits or patches are reported at this time.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 01:50 UTC

WeaknessesCWE-672

Technical details

References

Community reviews

Related threats