dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-54112

HIGH · 7.0 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 10.0.10240.21128 / 10.0.14393.8422 or later.
See remediation →
72/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
Use after free in Microsoft Virtual Hard Drive 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

Use after free vulnerability in Microsoft Virtual Hard Drive allows a locally authenticated attacker to elevate privileges to higher integrity levels by exploiting memory management in the VHD mounting subsystem.

MitigationApply Microsoft security updates for Virtual Hard Drive when available; until then, restrict local access to trusted users only and monitor for unusual VHD mounting 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 1507Operating system
Affected:< 10.0.10240.21128
Windows 10 1607Operating system
Affected:< 10.0.14393.8422
Windows 10 1809Operating system
Affected:< 10.0.17763.7792
Windows 10 21h2Operating system
Affected:< 10.0.19044.6332
Windows 10 22h2Operating system
Affected:< 10.0.19045.6332
Windows 11 22h2Operating system
Affected:< 10.0.22621.5909
Windows 11 23h2Operating system
Affected:< 10.0.22631.5909
Windows 11 24h2Operating system
Affected:< 10.0.26100.6508

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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. Check Windows version against affected ranges
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the installed Windows version and build number
    Affected if The version and build number fall below any of the listed thresholds for Windows 10 (1507, 1607, 1809, 21h2, 22h2) or Windows 11 (22h2, 23h2, 24h2)
  2. Verify Virtual Hard Drive component is present
    Check for the presence of vhd.sys driver in %SystemRoot%\System32\drivers\ or look for 'Microsoft Virtual Hard Drive' in the list of installed features via 'Get-WindowsOptionalFeature -Online' in PowerShell
    Affected if The VHD driver (vhd.sys) exists on the system, indicating the vulnerable component is installed
  3. Check for mounted VHDs
    Run 'Get-VHD -Path *' in PowerShell or check Disk Management (diskmgmt.msc) for any mounted virtual hard disk images
    Affected if Any VHD files are currently mounted or have been recently mounted on the system

A user is affected if they are running a Windows version below the specified build numbers AND the Virtual Hard Drive component is present and actively used on the system.

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.10240.21128 / 10.0.14393.8422 / 10.0.17763.7792 or later
Fixed in 10.0.10240.2112810.0.14393.842210.0.17763.7792
Interim mitigation

Apply Microsoft security updates for Virtual Hard Drive when available; until then, restrict local access to trusted users only and monitor for unusual VHD mounting activity.

Recommended fix High confidence

Install the specific security update for your Windows 10/11 version that includes the fix (versions listed in the affected products above - install 10.0.10240.21128 or higher for Win10 1507, 10.0.14393.8422 or higher for Win10 1607, etc.)

  1. 1. Identify the current Windows version by running 'winver' or checking Settings > System > About
  2. 2. Navigate to Windows Update (Settings > Update & Security > Windows Update)
  3. 3. Click 'Check for updates' to download and install the latest security updates
  4. 4. Alternatively, manually download the specific security update for your Windows version from the Microsoft Update Catalog (catalog.update.microsoft.com)
  5. 5. Search for the relevant KB article associated with CVE-2025-54112 for your specific Windows version
  6. 6. Restart the system after installing the update
Caveat Standard Windows security update - minimal risk; ensure backups of critical data before any system update

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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