dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-54912

HIGH · 7.8 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 →
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
Use after free in Windows BitLocker 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

A use-after-free vulnerability exists in Windows BitLocker that allows a locally authorized attacker to exploit freed memory to elevate privileges to higher integrity levels. The vulnerability stems from improper memory management in BitLocker's driver or related components, where memory is accessed after being deallocated.

MitigationApply Microsoft security patches for Windows systems once available. Prioritize patching endpoint systems where BitLocker is enabled, and restrict local administrator privileges to reduce attack surface.

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
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. Check Windows version and build number
    Run 'winver' or execute 'Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" | Select-Object DisplayVersion, CurrentBuild, CurrentBuildNumber' in PowerShell to retrieve the exact Windows version and build number
    Affected if The installed build number is below the fixed thresholds: < 10240.21128 (1507), < 14393.8422 (1607), < 17763.7792 (1809), < 19044.6332 (21h2), < 19045.6332 (22h2), < 22621.5909 (Win11 22h2), < 22631.5909 (Win11 23h2), < 26100.6508 (Win11 24h2)
  2. Verify BitLocker is enabled
    Run 'manage-bde -status' or execute 'Get-BitLockerVolume -MountPoint C:' in PowerShell to check if BitLocker protection is active on any volume
    Affected if BitLocker protection status shows 'Encryption in Progress' or 'Encryption Complete' on any volume, indicating BitLocker is enabled on the system

You are affected if your Windows build is below the fixed version AND BitLocker is enabled on your system, as the use-after-free only triggers in the BitLocker driver when that feature is active.

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 patches for Windows systems once available. Prioritize patching endpoint systems where BitLocker is enabled, and restrict local administrator privileges to reduce attack surface.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21128 or later | Windows 10 1607: 10.0.14393.8422 or later | Windows 10 1809: 10.0.17763.7792 or later | Windows 10 21h2: 10.0.19044.6332 or later | Windows 10 22h2: 10.0.19045.6332 or later | Windows 11 22h2: 10.0.22621.5909 or later | Windows 11 23h2: 10.0.22631.5909 or

  1. Identify your current Windows version and build by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine if your current build is below the fixed version for your Windows release
  3. Apply the appropriate Windows security update via Windows Update, or manually download and install the relevant Cumulative Security Update from the Microsoft Update Catalog for your specific Windows version
  4. After installation, restart the system to complete the patch
Caveat Standard Windows security update; no breaking changes expected for typical configurations

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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