dbcve.org
NULL Pointer DereferenceWeakness · CWE-476

CVE-2025-0009

MEDIUM · 5.5 CVSS v3.1 Published 2025-09-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A NULL pointer dereference in AMD Crash Defender could allow an attacker to write a NULL output to a log file potentially resulting in a system crash and loss of availability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A NULL pointer dereference vulnerability in AMD Crash Defender allows an attacker to write a NULL output to a log file, which can trigger a system crash leading to loss of availability. The vulnerability has a CVSS score of 5.5 (Medium) and primarily impacts system availability.

MitigationApply the AMD-provided security patch for Crash Defender when available. Check AMD's security advisory page and ensure all affected AMD Crash Defender installations are updated to the patched version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify AMD Crash Defender is installed
    Check for AMD Crash Defender installation by looking for its executable or service. On Windows, check Program Files for 'AMD Crash Defender' folder or look for 'AMDCrashDefender.exe' in system directories. On Linux, check /opt or /usr/lib for amd-crash-defender components.
    Affected if AMD Crash Defender software is present on the system
  2. Identify the installed version
    Run the AMD Crash Defender executable with version flag (e.g., 'AMDCrashDefender.exe --version' or check the file properties of the main executable). Alternatively, check the Windows Registry under HKLM\SOFTWARE\AMD\CrashDefender or the application's log files for version information.
    Affected if The version cannot be determined or is earlier than the patched version referenced in AMD security advisories
  3. Confirm logging feature is enabled
    Examine AMD Crash Defender configuration files (typically in the installation directory or %APPDATA%\AMD\CrashDefender) for logging settings. Check if log file output is configured and active. Also verify log file locations for recent activity.
    Affected if Logging to file is enabled and the application writes to log files (the vulnerability triggers when NULL output is written to logs)
  4. Review system crash logs for anomalies
    Check Windows Event Viewer for Application or System logs around the time of any crashes. Also examine AMD Crash Defender's own log files for entries containing NULL, empty values, or error patterns indicating the vulnerability was triggered.
    Affected if Recent system crashes correspond with AMD Crash Defender activity and log entries show abnormal NULL handling
  5. Compare against AMD security advisories
    Visit AMD's official security advisory page and compare your installed version against the fixed version listed for CVE-2025-0009. AMD typically publishes the specific version number that addresses each vulnerability.
    Affected if The installed version is lower than the patched version specified in AMD's advisory for this CVE

You are affected if AMD Crash Defender is installed with an unpatched version and the logging feature is enabled, allowing the NULL pointer dereference to trigger when the application writes to log files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the AMD-provided security patch for Crash Defender when available. Check AMD's security advisory page and ensure all affected AMD Crash Defender installations are updated to the patched version.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0009 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0009 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data