dbcve.org
Windows 11 23h2Operating system · Microsoft

CVE-2025-62465

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.20348.4467 / 10.0.22631.6345 or later.
See remediation →
67/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
Null pointer dereference in Windows DirectX allows an authorized attacker to deny service locally.

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 exists in Windows DirectX that can be triggered by an authorized local attacker, causing a denial of service (likely a crash or Blue Screen of Death). The vulnerability stems from improper pointer validation within DirectX components, leading to a NULL pointer dereference when processing certain operations.

MitigationApply Microsoft security updates for Windows when released. Until a patch is available, restrict local access to untrusted authorized users and monitor for system instability related to DirectX applications.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 11 23h2Operating system
Affected:< 10.0.22631.6345
Windows 11 24h2Operating system
Affected:< 10.0.26100.7392
Windows 11 25h2Operating system
Affected:< 10.0.26200.7392
Windows Server 2022Operating system
Affected:< 10.0.20348.4467
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.2025
Windows Server 2025Operating system
Affected:< 10.0.26100.7392

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
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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. Identify Windows build version
    Run 'winver' from command prompt or check System Properties, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the full build number including the KB suffix
    Affected if The build version is lower than the affected thresholds (10.0.22631.6345 for 23h2, 10.0.26100.7392 for 24h2/Server 2025, 10.0.26200.7392 for 25h2, 10.0.20348.4467 for Server 2022, 10.0.25398.2025 for Server 2022 23h2)
  2. Confirm Windows edition
    Run 'winver' or check System Properties to determine if the system is Windows 11 23h2, 24h2, 25h2, Server 2022, Server 2022 23h2, or Server 2025
    Affected if The edition matches one of the affected product versions AND the build number is below the corresponding threshold
  3. Verify DirectX is in use
    Check for running applications that use DirectX (games, multimedia apps, Direct3D applications) using Task Manager or by reviewing installed programs
    Affected if DirectX-enabled applications are actively used on the system - this is the attack surface for triggering the vulnerability

The system is affected if it runs any of the listed Windows editions/builds lower than the specified version thresholds and uses DirectX or allows local authorized users to run DirectX applications.

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.

dbcve · scoped
Upgrade available Upgrade to 10.0.20348.4467 / 10.0.22631.6345 / 10.0.25398.2025 or later
Fixed in 10.0.20348.446710.0.22631.634510.0.25398.2025
Interim mitigation

Apply Microsoft security updates for Windows when released. Until a patch is available, restrict local access to untrusted authorized users and monitor for system instability related to DirectX applications.

Recommended fix High confidence

Windows 11 23h2: build 10.0.22631.6345 or later | Windows 11 24h2: build 10.0.26100.7392 or later | Windows 11 25h2: build 10.0.26200.7392 or later | Windows Server 2022: build 10.0.20348.4467 or later | Windows Server 2022 23h2: build 10.0.25398.2025 or later | Windows Server 2025: build 10.0.26100

  1. Identify the current Windows build version by running 'winver' or 'systeminfo' from command prompt
  2. Determine which Windows version and build you are running (11 23h2, 11 24h2, 11 25h2, Server 2022, Server 2022 23h2, or Server 2025)
  3. Open Windows Settings > Windows Update and check for updates
  4. Install all available cumulative updates, or manually download and install the specific KB that addresses CVE-2025-62465 from the Microsoft Update Catalog
  5. Verify the build number has been updated to one of: 10.0.22631.6345 or higher (Win11 23h2), 10.0.26100.7392 or higher (Win11 24h2/Server 2025), 10.0.26200.7392 or higher (Win11 25h2), 10.0.20348.4467 or higher (Server 2022), 10.0.25398.2025 or higher (Server 2022 23h2)
  6. Restart the system as prompted to complete the update installation
Caveat Standard Windows cumulative update; review release notes for any known compatibility issues before deployment in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 11 23h2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62465 — 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-62465 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