dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-47982

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.14393.8246 / 10.0.17763.7558 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 input validation in Windows Storage VSP 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 · high confidence

Improper input validation in the Windows Storage VSP (Virtual Service Provider) Driver enables a local, authorized attacker to elevate privileges. This kernel-level driver vulnerability allows an attacker with basic system access to execute code with elevated (SYSTEM) privileges by sending specially crafted input to the storage VSP driver.

MitigationApply the Microsoft security update for CVE-2025-47982 promptly. Until patched, minimize the number of users with local access and monitor for suspicious process creation or privilege escalation activity.

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.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652
Windows Server 2016Operating system
Affected:< 10.0.14393.8246

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. Determine Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows version and build number
    Affected if The build number is lower than any of these thresholds: 14393.8246 (Windows 10 1607/Server 2016), 17763.7558 (Windows 10 1809), 19044.6093 (Windows 10 21h2), 19045.6093 (Windows 10 22h2), 22621.5624 (Windows 11 22h2), 22631.5624 (Windows 11 23h2), or 26100.4652 (Windows 11 24h2)
  2. Identify if Storage VSP driver is present
    Run 'sc query svsp' in Command Prompt or check driver existence via 'driverquery /v | findstr -i svsp' to determine if the Storage VSP driver is loaded on the system
    Affected if The Storage VSP driver (svsp) is present and running on an affected Windows version as determined in step 1
  3. Verify current patch state via system information
    Run 'systeminfo' and examine the 'Hotfix(s)' section or check Windows Update history to confirm whether KB5057294 or subsequent security updates have been applied
    Affected if The system shows no relevant security update installed for CVE-2025-47982 and the OS version falls within the affected ranges from step 1

A system is affected if it runs any of the listed Windows versions below the specified build numbers AND has the Storage VSP driver loaded, without the CVE-2025-47982 security update applied.

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.8246 / 10.0.17763.7558 / 10.0.19044.6093 or later
Fixed in 10.0.14393.824610.0.17763.755810.0.19044.6093
Interim mitigation

Apply the Microsoft security update for CVE-2025-47982 promptly. Until patched, minimize the number of users with local access and monitor for suspicious process creation or privilege escalation activity.

Recommended fix High confidence

Install the relevant Windows security update (KB) from Microsoft's monthly patch cycle that addresses CVE-2025-47982

  1. Open Settings on the Windows system and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Alternatively, use WSUS (Windows Server Update Services) to deploy the relevant security update to managed systems
  4. Alternatively, manually download the security update from the Microsoft Update Catalog by searching for the KB associated with this CVE
  5. Restart the system after the update is installed to ensure the Windows Storage VSP Driver patch is fully applied
  6. Verify the installed OS build version matches or exceeds the fixed version for your Windows release (e.g., 10.0.14393.8246 for Windows 10 1607/Server 2016, 10.0.17763.7558 for Windows 10 1809, etc.)

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
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,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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