dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-24059

HIGH · 7.8 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 10.0.10240.20947 / 10.0.14393.7876 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
Incorrect conversion between numeric types in Windows Common Log File System 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

A type conversion vulnerability exists in the Windows Common Log File System Driver (CLFS.sys) where incorrect conversion between numeric types allows a locally authenticated attacker to elevate privileges to SYSTEM or similar elevated context.

MitigationApply the Microsoft security update for CVE-2025-24059 through standard Windows Update or patch management infrastructure. Verify the CLFS.sys driver version matches the patched version after 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 1507Operating system
Affected:< 10.0.10240.20947
Windows 10 1607Operating system
Affected:< 10.0.14393.7876
Windows 10 1809Operating system
Affected:< 10.0.17763.7009
Windows 10 21h2Operating system
Affected:< 10.0.19044.5608
Windows 10 22h2Operating system
Affected:< 10.0.19045.5608
Windows 11 22h2Operating system
Affected:< 10.0.22621.5039
Windows 11 23h2Operating system
Affected:< 10.0.22631.5039
Windows 11 24h2Operating system
Affected:< 10.0.26100.3403> 10.0.26100.3403, < 10.0.26100.3476

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. 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 Windows build number falls below any of the thresholds listed in the CVE (e.g., below 10.0.10240.20947 for 1507, below 10.0.19045.5608 for 10 22h2, etc.)
  2. Locate CLFS.sys driver file
    The driver is located at C:\Windows\System32\drivers\CLFS.sys. Verify the file exists using 'Test-Path C:\Windows\System32\drivers\CLFS.sys'
    Affected if The CLFS.sys file exists on the system, which is the case for all supported Windows installations
  3. Retrieve CLFS.sys file version
    Run 'Get-ItemProperty C:\Windows\System32\drivers\CLFS.sys | Select-Object VersionInfo' or use 'driverquery /v /fo csv | Select-String CLFS' to obtain the driver version
    Affected if The returned file version is lower than the patched version for your specific Windows release (e.g., for Windows 10 22h2, version < 10.0.19045.5608)
  4. Verify driver signature status
    Run 'Get-AuthenticodeSignature C:\Windows\System32\drivers\CLFS.sys' to check if the driver is properly signed
    Affected if The driver is present and its version matches the vulnerable version ranges for your Windows build

A system is affected if it runs any of the listed Windows versions AND has a CLFS.sys version below the patched threshold for that specific Windows release.

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.20947 / 10.0.14393.7876 / 10.0.17763.7009 or later
Fixed in 10.0.10240.2094710.0.14393.787610.0.17763.7009
Interim mitigation

Apply the Microsoft security update for CVE-2025-24059 through standard Windows Update or patch management infrastructure. Verify the CLFS.sys driver version matches the patched version after deployment.

Recommended fix High confidence

Windows security update containing the fix for CVE-2025-24059 (specific to each Windows version: e.g., Windows 10 22h2 requires build >=10.0.19045.5608, Windows 11 24h2 requires build >=10.0.26100.3476)

  1. Identify current Windows version and build number by running 'winver' or 'systeminfo'
  2. Locate and install the appropriate Windows security update for CVE-2025-24059 from Microsoft Update Catalog or Windows Update
  3. After installation, restart the system to apply the kernel driver patch
  4. Verify the fix by checking that the system build matches or exceeds the fixed version for your Windows release

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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