dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-60708

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 10.0.14393.8594 / 10.0.17763.8027 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
Untrusted pointer dereference in Storvsp.sys Driver 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 · high confidence

This is an untrusted pointer dereference vulnerability in Microsoft's Storvsp.sys storage virtual driver. A locally authorized attacker can exploit this kernel-mode driver flaw to dereference an untrusted pointer, causing a denial of service (system crash or hang). The vulnerability requires local access with authorization, not remote exploitation.

MitigationApply the Microsoft security update for CVE-2025-60708 to patch the Storvsp.sys driver. As a kernel driver vulnerability, patching is the primary remediation; investigate affected systems running the Storvsp driver and validate the patch deployment.

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 1607Operating system
Affected:< 10.0.14393.8594
Windows 10 1809Operating system
Affected:< 10.0.17763.8027
Windows 10 21h2Operating system
Affected:< 10.0.19044.6575
Windows 10 22h2Operating system
Affected:< 10.0.19045.6575
Windows 11 23h2Operating system
Affected:< 10.0.22631.6199
Windows 11 24h2Operating system
Affected:< 10.0.26100.7092
Windows 11 25h2Operating system
Affected:< 10.0.26200.7092
Windows Server 2016Operating system
Affected:< 10.0.14393.8594

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 version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the exact Windows version and build number
    Affected if The OS version falls within the affected ranges listed in the CVE (Windows 10 1607-22h2, Windows 11 23h2-25h2, or Windows Server 2016)
  2. Locate Storvsp.sys driver file
    Search for the driver file: 'dir /s C:\Windows\System32\drivers\Storvsp.sys' or 'Get-ChildItem -Path C:\ -Recurse -Filter Storvsp.sys -ErrorAction SilentlyContinue'
    Affected if The Storvsp.sys file exists on the system, indicating the vulnerable driver component is present
  3. Retrieve Storvsp.sys file version
    Right-click the driver file, select Properties > Details, or run 'powershell (Get-Item "C:\Windows\System32\drivers\Storvsp.sys").VersionInfo.FileVersion'
    Affected if The driver version is found and is lower than the patched version threshold for your specific Windows build (see version list in CVE)
  4. Compare against vulnerable version ranges
    Match your OS build to the corresponding threshold: 14393.8594 (Win10 1607/Server 2016), 17763.8027 (Win10 1809), 19044.6575 (Win10 21h2), 19045.6575 (Win10 22h2), 22631.6199 (Win11 23h2), 26100.7092 (Win11 24h2), 26200.7092 (Win11 25h2)
    Affected if Your installed Storvsp.sys version is below the threshold for your Windows version, meaning the system is vulnerable

A system is affected if it runs any of the listed Windows versions with Storvsp.sys present and the driver version is below the patched threshold for that specific Windows build.

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.14393.8594 / 10.0.17763.8027 / 10.0.19044.6575 or later
Fixed in 10.0.14393.859410.0.17763.802710.0.19044.6575
Interim mitigation

Apply the Microsoft security update for CVE-2025-60708 to patch the Storvsp.sys driver. As a kernel driver vulnerability, patching is the primary remediation; investigate affected systems running the Storvsp driver and validate the patch deployment.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.8594+ | Windows 10 1809: 10.0.17763.8027+ | Windows 10 21h2: 10.0.19044.6575+ | Windows 10 22h2: 10.0.19045.6575+ | Windows 11 23h2: 10.0.22631.6199+ | Windows 11 24h2: 10.0.26100.7092+ | Windows 11 25h2: 10.0.26200.7092+ | Windows Server 2016: 10.0.14393.8594+

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Note the build number (e.g., 10.0.19045.xxxx)
  3. Compare against the vulnerable versions listed: Windows 10 1607 (<10.0.14393.8594), Windows 10 1809 (<10.0.17763.8027), Windows 10 21h2 (<10.0.19044.6575), Windows 10 22h2 (<10.0.19045.6575), Windows 11 23h2 (<10.0.22631.6199), Windows 11 24h2 (<10.0.26100.7092), Windows 11 25h2 (<10.0.26200.7092), Windows Server 2016 (<10.0.14393.8594)
  4. Open Windows Update by going to Settings > Update & Security > Windows Update or running 'ms-settings:windowsupdate'
  5. Click 'Check for updates' and install all available updates
  6. Restart the system when prompted to complete the installation of the Storvsp.sys driver update
  7. Verify the fix by checking the installed build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update with reboot required; no application compatibility issues expected for this kernel driver patch

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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