CVE-2025-0011VulnerabilityPublished 6 Sep 2025Updated 8 Sep 2025

CVE-2025-0011: AMD Ryzen™ 8000 Series Desktop Processors · Improper Removal of Sensitive Information Before Storage or Transfer

Affects AMD Ryzen™ 8000 Series Desktop ProcessorsSource CVE Database V5

Not known to be exploited · CVSS 3.3 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

3.3Low

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

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

Attack Vector: Local: The vulnerable component 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 remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-26.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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.

What to do

AI-suggested

1. Apply patches and firmware updates from AMD as soon as they become available to address the improper data removal in Crash Defender. 2. Restrict local access to systems running AMD Ryzen 8000 Series processors by enforcing strict access controls and endpoint security policies. 3. Employ robust privilege management to minimize the number of users with local privileges that could exploit this vulnerability. 4. Use security monitoring tools to detect unusual local activity that might indicate attempts to exploit kernel information leaks. 5. Consider enabling additional kernel protection mechanisms such as Kernel Page Table Isolation (KPTI) and enhanced KASLR implementations where possible. 6. Conduct regular security audits and vulnerability assessments on endpoints to ensure no unauthorized local access is possible. 7. Educate users and administrators about the risks of local privilege misuse and the importance of maintaining updated systems.

Description

Improper removal of sensitive information before storage or transfer in AMD Crash Defender could allow an attacker to obtain kernel address information potentially resulting in loss of confidentiality.

Impact

For European organizations, the impact of CVE-2025-0011 is primarily a potential confidentiality breach of kernel address information on systems running AMD Ryzen™ 8000 Series Desktop Processors. While the direct impact is limited, the exposure of kernel addresses can facilitate more advanced attacks such as privilege escalation or bypassing security mitigations. Organizations with sensitive workloads or those relying on AMD Ryzen 8000 series in desktop environments (e.g., developer workstations, administrative consoles) could see increased risk if attackers gain local access. However, since exploitation requires local privileges and does not affect server-grade processors directly, the threat is somewhat contained. Still, in environments where endpoint security is critical, such as financial institutions, government agencies, or critical infrastructure operators in Europe, this vulnerability could be a stepping stone for attackers to gain deeper system access. The lack of known exploits reduces immediate risk, but the presence of this vulnerability necessitates vigilance and proactive mitigation.

CWE-212Improper Removal of Sensitive Information Before Storage or Transfer (opens in a new tab)
Base weakness
The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.
Requirements
Clearly specify which information should be regarded as private or sensitive, and require that the product offers functionality that allows the user to cleanse the sensitive information from the resource before it is published or exported to other parties.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Implementation · Operation · Attack Surface Reduction
Some tools can automatically analyze documents to redact, strip, or "sanitize" private information, although some human review might be necessary. Tools may vary in terms of which document formats can be processed.
OWASP ASVS 4.0.3
V8.3.2 (opens in a new tab)
Attack patterns
Windows ::DATA Alternate Data Stream (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

amd.com/en/resources/product-security/bulletin/AMD-SB-6018.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 15 Sep 2025, 00:41 UTC

WeaknessesCWE-212

Technical details

References

Community reviews

Related threats