dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 1 Apr 2025.
Windows 10 1507Operating system · Microsoft

CVE-2025-24985

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 →
97/100
Remediation priority · Urgent
In the wild Public exploit No privileges Patch available

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
Integer overflow or wraparound in Windows Fast FAT Driver allows an unauthorized attacker to execute code 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 integer overflow vulnerability in the Windows Fast FAT filesystem driver. The flaw allows a local attacker to potentially execute arbitrary code by exploiting the arithmetic wraparound condition in the driver, likely through specially crafted filesystem operations.

MitigationApply the Microsoft security update for CVE-2025-24985 once released. Prioritize patching systems where untrusted FAT media may be mounted.

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

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 your Windows version and build number
    Run 'winver' from the Run dialog or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' in Command Prompt. Note the full build number (e.g., 10.0.19045.5608).
    Affected if The reported build number is LOWER than the threshold for your Windows release (see affected version ranges).
  2. Confirm fat.sys driver presence
    Open File Explorer and navigate to C:\Windows\System32\drivers\fat.sys, or run 'dir C:\Windows\System32\drivers\fat.sys' in Command Prompt.
    Affected if The file exists on the system. The driver is present by default in standard Windows installations.
  3. Retrieve fat.sys file version
    Right-click fat.sys, select Properties, then view the Details tab for File Version. Alternatively, run 'powershell (Get-Item C:\Windows\System32\drivers\fat.sys).VersionInfo' to retrieve version information.
    Affected if The file version is present. Compare this version against Microsoft's security bulletin for CVE-2025-24985 to confirm if it contains the fix.
  4. Check Windows Update for security patches
    Open Settings > Windows Update > Update history. Search for security updates installed around the CVE disclosure date. Look for KB entries containing security fixes.
    Affected if No relevant security update for CVE-2025-24985 has been installed, and the Windows build version falls within the affected ranges.

You are affected if your Windows build number is lower than the specified threshold for your Windows release AND you have not applied the corresponding security update for CVE-2025-24985.

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
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security update for CVE-2025-24985 once released. Prioritize patching systems where untrusted FAT media may be mounted.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.20947 | Windows 10 1607: 10.0.14393.7876 | Windows 10 1809: 10.0.17763.7009 | Windows 10 21h2: 10.0.19044.5608 | Windows 10 22h2: 10.0.19045.5608 | Windows 11 22h2: 10.0.22621.5039 | Windows 11 23h2: 10.0.22631.5039 | Windows 11 24h2: 10.0.26100.3403

  1. Open Windows Settings and navigate to Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Restart the system after updates are installed
  4. Verify the installed updates by running 'winver' command to confirm the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows security update - minimal risk; ensure backups of critical data before applying

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

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,060
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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