Skip to content
Server Security Center
KEVhigh7.8

CVE-2025-24985: Microsoft Windows Fast FAT File System Driver Integer Overflow

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2025-03-11.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
3.9%
higher than 90.5% of all CVEs
Added to CISA KEV
2025-03-11
US federal due date 2025-04-01
Automatable (CISA SSVC)
no
technical impact: total

CVE-2025-24985 explained

CVE-2025-24985 is an integer overflow or wraparound in the Windows Fast FAT File System Driver. It lets an unauthorized attacker execute code locally on affected Windows client and server versions. CISA lists it as known to be exploited, so affected systems should be patched promptly.

Impact

An attacker can execute code locally. This can lead to high loss of confidentiality, integrity and availability. No privileges are required, but user interaction is required and the attack vector is local. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so attacks at scale need manual steps. Attackers are known to exploit this vulnerability.

Who is affected

Affected builds include Windows 10 Version 1507 before 10.0.10240.20947, 1607 before 10.0.14393.7876, 1809 before 10.0.17763.7009, 21H2 before 10.0.19044.5608 and 22H2 before 10.0.19045.5608. Windows 11 22H2 is fixed in 10.0.22621.5039, and 22H3 and 23H2 in 10.0.22631.5039. Windows 11 24H2 is fixed in 10.0.26100.3476. Windows Server 2008 R2 SP1, including Server Core, is fixed in 6.1.7601.27618. Windows Server 2008 SP2 is fixed in 6.0.6003.23168. Further products are listed on this page.

Written with AI from the data on this page and checked against it automatically.

Official description

Integer overflow or wraparound in Windows Fast FAT Driver allows an unauthorized attacker to execute code locally.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.20947
    Fixed in
    • 10.0.10240.20947
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.7876
    Fixed in
    • 10.0.14393.7876
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.7009
    Fixed in
    • 10.0.17763.7009
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.5608
    Fixed in
    • 10.0.19044.5608
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.5608
    Fixed in
    • 10.0.19045.5608
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.5039
    Fixed in
    • 10.0.22621.5039
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.5039
    Fixed in
    • 10.0.22631.5039
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.5039
    Fixed in
    • 10.0.22631.5039
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.3476
    Fixed in
    • 10.0.26100.3476
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.27618
    Fixed in
    • 6.1.7601.27618
Show 15 more products
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.27618
    Fixed in
    • 6.1.7601.27618
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.23168
    Fixed in
    • 6.0.6003.23168
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.23168
    Fixed in
    • 6.0.6003.23168
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25368
    Fixed in
    • 6.2.9200.25368
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25368
    Fixed in
    • 6.2.9200.25368
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22470
    Fixed in
    • 6.3.9600.22470
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22470
    Fixed in
    • 6.3.9600.22470
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.7876
    Fixed in
    • 10.0.14393.7876
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.7876
    Fixed in
    • 10.0.14393.7876
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.7009
    Fixed in
    • 10.0.17763.7009
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.7009
    Fixed in
    • 10.0.17763.7009
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.3328
    Fixed in
    • 10.0.20348.3328
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1486
    Fixed in
    • 10.0.25398.1486
  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.3476
    Fixed in
    • 10.0.26100.3476
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.3476
    Fixed in
    • 10.0.26100.3476

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.20947
    • Microsoft Windows 10 Version 1607: 10.0.14393.7876
    • Microsoft Windows 10 Version 1809: 10.0.17763.7009
    • Microsoft Windows 10 Version 21H2: 10.0.19044.5608
    • Microsoft Windows 10 Version 22H2: 10.0.19045.5608
    • Microsoft Windows 11 version 22H2: 10.0.22621.5039
    Fixed versions for 19 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2025-24985
  • CISA's deadline for US federal agencies: 2025-04-01 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install Microsoft's security update so each system reaches at least the fixed build listed for its Windows version.
  2. Follow the Microsoft advisory for all affected products, including those listed further on this page.
  3. Prioritize patching, as CISA lists this vulnerability as known exploited; US federal agencies had a due date of 2025-04-01.
  4. Apply mitigations per vendor instructions, or discontinue use of the product if mitigations are unavailable, as CISA requires.
  5. Check unpatched systems for signs of compromise.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-190 Integer Overflow or Wraparound, CWE-122 Heap-based Buffer Overflow

Questions about CVE-2025-24985

Is CVE-2025-24985 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-03-11. Whether it is used in ransomware campaigns is unknown.
Can it be exploited remotely?
The attack vector is local and user interaction is required. No privileges are needed. CISA rates it as not automatable.
Which build fixes it on Windows 11 24H2?
The CVE record lists 10.0.26100.3476 as the fixed build for Windows 11 Version 24H2.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.