dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-64673

HIGH · 7.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.17763.8146 / 10.0.19044.6691 or later.
See remediation →
80/100
Remediation priority · High
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
Improper access control in Storvsp.sys Driver allows an authorized attacker to elevate privileges 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

Improper access control in the Storvsp.sys Windows kernel-mode driver allows a local attacker with existing authorization to escalate privileges, potentially achieving administrative or SYSTEM-level access. The vulnerability stems from the driver failing to properly validate user permissions before granting access to privileged operations or memory regions.

MitigationApply vendor-provided patches or updates to the Storvsp.sys driver. If no patch is available, restrict authorized user access to the system, or consider disabling or removing the driver if unused.

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 10 1809Operating system
Affected:< 10.0.17763.8146
Windows 10 21h2Operating system
Affected:< 10.0.19044.6691
Windows 10 22h2Operating system
Affected:< 10.0.19045.6691
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 2019Operating system
Affected:< 10.0.17763.8146
Windows Server 2022Operating system
Affected:< 10.0.20348.4467

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Locate the Storvsp.sys driver file
    Search for Storvsp.sys on the system using file search or command: 'dir /s C:\Storvsp.sys' or 'Get-ChildItem -Path C:\ -Recurse -Filter Storvsp.sys -ErrorAction SilentlyContinue'
    Affected if The driver file is not found on the system (not affected, driver not present)
  2. Retrieve the driver file version
    Right-click the Storvsp.sys file, select Properties, then Details tab to view File Version. Alternatively, use PowerShell: '(Get-Item "C:\Windows\System32\drivers\Storvsp.sys").VersionInfo.FileVersion'
    Affected if The driver version number is lower than the patched version for your Windows version (see affected ranges)
  3. Identify the installed Windows version
    Run 'winver' from Run dialog, or use 'systeminfo' in Command Prompt, or PowerShell: '[System.Environment]::OSVersion.Version'
    Affected if The Windows version matches one of the affected products listed in the CVE advisory
  4. Compare against affected version ranges
    Cross-reference the driver file version with the version thresholds: Windows 10 1809/Server 2019 needs >=10.0.17763.8146, Windows 10 21h2 needs >=10.0.19044.6691, Windows 10 22h2 needs >=10.0.19045.6691, Windows 11 23h2 needs >=10.0.22631.6345, Windows 11 24h2 needs >=10.0.26100.7392, Windows 11 25h2 needs >=10.0.26200.7392, Windows Server 2022 needs >=10.0.20348.4467
    Affected if The installed driver version falls below the threshold for your specific Windows version

The system is affected if Storvsp.sys is present AND the installed driver version is lower than the required patch version for the detected Windows version.

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.17763.8146 / 10.0.19044.6691 / 10.0.19045.6691 or later
Fixed in 10.0.17763.814610.0.19044.669110.0.19045.6691
Interim mitigation

Apply vendor-provided patches or updates to the Storvsp.sys driver. If no patch is available, restrict authorized user access to the system, or consider disabling or removing the driver if unused.

Recommended fix High confidence

Install the applicable Windows Security Update containing the CVE-2025-64673 patch for your specific Windows version (KB reference available via MSRC)

  1. Open Settings > Update & Security > Windows Update on the affected Windows system
  2. Click 'Check for updates' to download and install all available security updates
  3. After updates install, verify the system build number matches or exceeds the fixed version for your Windows release: For Windows 10 1809/Server 2019: 10.0.17763.8146, Windows 10 21h2: 10.0.19044.6691, Windows 10 22h2: 10.0.19045.6691, Windows 11 23h2: 10.0.22631.6345, Windows 11 24h2: 10.0.26100.7392, Windows 11 25h2: 10.0.26200.7392, Windows Server 2022: 10.0.20348.4467
  4. Restart the system to complete the update installation
  5. Confirm the Storvsp.sys version reflects the patched build via 'winver' or system information
Caveat Standard Windows update risks apply - ensure backups and test in staging if possible; no major functional changes expected from this security patch

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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