CVE-2025-21180 — Windows exFAT File System Remote Code Execution Vulnerability
Executive Summary
Heap-based buffer overflow in Windows exFAT File System allows an unauthorized attacker to execute code locally.
Overview
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
EPSS Score
Affected Products
| Product | KB Article | Severity | Impact | Restart Required |
|---|---|---|---|---|
| Windows 10 for 32-bit Systems | 5053618 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 for x64-based Systems | 5053618 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 1607 for 32-bit Systems | 5053594 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 1607 for x64-based Systems | 5053594 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 1809 for 32-bit Systems | 5053596 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 1809 for x64-based Systems | 5053596 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 21H2 for 32-bit Systems | 5053606 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 21H2 for ARM64-based Systems | 5053606 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 21H2 for x64-based Systems | 5053606 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 22H2 for 32-bit Systems | 5053606 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 22H2 for ARM64-based Systems | 5053606 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 22H2 for x64-based Systems | 5053606 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 11 Version 22H2 for ARM64-based Systems | 5053602 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 11 Version 22H2 for x64-based Systems | 5053602 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 11 Version 23H2 for ARM64-based Systems | 5053602 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 11 Version 23H2 for x64-based Systems | 5053602 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 11 Version 24H2 for ARM64-based Systems 5053598 (Security Update) 5053636 (SecurityHotpatchUpdate) Important Remote Code Execution 5051987 5052105 Base: 7.8 Temporal: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 10.0.26100.3476 10.0.26100.3403 Yes None Windows 11 Version 24H2 for x64-based Systems 5053598 (Security Update) 5053636 (SecurityHotpatchUpdate) Important Remote Code Execution 5051987 5052105 Base: 7.8 Temporal: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 10.0.26100.3476 10.0.26100.3403 Yes None Windows Server 2008 for 32-bit Systems Service Pack 2 5053888 (Monthly Rollup) 5053995 (Security Only) Important Remote Code Execution 5052038 Base: 7.8 Temporal: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.0.6003.23168 Yes None Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation) 5053888 (Monthly Rollup) 5053995 (Security Only) Important Remote Code Execution 5052038 Base: 7.8 Temporal: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.0.6003.23168 Yes None Windows Server 2008 for x64-based Systems Service Pack 2 5053888 (Monthly Rollup) 5053995 (Security Only) Important Remote Code Execution 5052038 Base: 7.8 Temporal: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.0.6003.23168 Yes None Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation) 5053888 (Monthly Rollup) 5053995 (Security Only) Important Remote Code Execution 5052038 Base: 7.8 Temporal: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.0.6003.23168 Yes None Windows Server 2008 R2 for x64-based Systems Service Pack 1 5053620 (Monthly Rollup) 5053627 (Security Only) Important Remote Code Execution 5052016 Base: 7.8 Temporal: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.1.7601.27618 Yes None Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation) 5053620 (Monthly Rollup) 5053627 (Security Only) Important Remote Code Execution 5052016 Base: 7.8 Temporal: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 6.1.7601.27618 Yes None Windows Server 2012 | 5053886 (Monthly Rollup) |
Important | Remote Code Execution | Yes |
| Windows Server 2012 (Server Core installation) | 5053886 (Monthly Rollup) |
Important | Remote Code Execution | Yes |
| Windows Server 2012 R2 | 5053887 (Monthly Rollup) |
Important | Remote Code Execution | Yes |
| Windows Server 2012 R2 (Server Core installation) | 5053887 (Monthly Rollup) |
Important | Remote Code Execution | Yes |
| Windows Server 2016 | 5053594 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows Server 2016 (Server Core installation) | 5053594 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows Server 2019 | 5053596 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows Server 2019 (Server Core installation) | 5053596 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows Server 2022 5053603 (Security Update) 5053638 (SecurityHotpatchUpdate) Important Remote Code Execution 5051979 5052106 Base: 7.8 Temporal: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 10.0.20348.3328 10.0.20348.3270 Yes None Windows Server 2022 (Server Core installation) 5053603 (Security Update) 5053638 (SecurityHotpatchUpdate) Important Remote Code Execution 5051979 5052106 Base: 7.8 Temporal: 6.8 Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 10.0.20348.3328 10.0.20348.3270 Yes None Windows Server 2022, 23H2 Edition (Server Core installation) | 5053599 (Security Update) |
Important | Remote Code Execution | Yes |
Patches
| Article | Type | Restart |
|---|---|---|
5053618 |
Security Update | Yes |
5053594 |
Security Update | Yes |
5053596 |
Security Update | Yes |
5053606 |
Security Update | Yes |
5053602 |
Security Update | Yes |
5053886 |
Monthly Rollup | Yes |
5053887 |
Monthly Rollup | Yes |
5053599 |
Security Update | Yes |
Patch Diff
Integer overflow leading to a heap-based buffer overflow (CWE-122) in the Windows exFAT file-system driver exfat.sys, mount-time arbitrary code execution (Important, RCE, AV:L, UI:R, CVSS 7.8, Exploitation More Likely). When an exFAT volume is mounted, FppSetupAllocationSupport derives the allocation-bitmap support parameters from untrusted on-disk metadata and sizes the in-memory allocation structures. PRE: it took a 32-bit count/length from the volume (param_2 + 0x138) and rounded it up by adding 0xffff WITHOUT an overflow check, so a crafted volume supplying a value near 0xFFFFFFFF wrapped the 32-bit addition to a small number, producing an undersized heap allocation that was then overrun when the structures were populated - a heap overflow reachable at mount time. Because exFAT parses the volume when it is mounted, an attacker who tricks a local user into mounting a malicious VHD (AV:L, UI:R) can trigger the overflow for kernel code execution. Diff of exfat.sys 10.0.26100.2454 -> .3470 (Mar 11 2025, KB5053598) confirms the fix: FppSetupAllocationSupport gains an overflow guard gated behind CFR flag Feature_930095419 - if (uVar7 + 0xffff < uVar7) it sets STATUS_FILE_CORRUPT_ERROR (0xc0000102) and calls ExRaiseStatus() to abort the mount before the undersized allocation is made. (Wide .2454->.3470 span that also linked in CFR feature-usage instrumentation; the security-relevant change is the overflow guard.)
| Function | Address | Change | Note |
|---|---|---|---|
FppSetupAllocationSupport |
code change |
code (adds +0xffff rounding overflow guard, CFR-gated) | Pre: allocation-support size computed as volume_count + 0xffff in 32-bit with no overflow check -> near-UINT_MAX count wraps to a tiny size -> undersized heap allocation -> overflow. Post (Feature_930095419): if (uVar7 + 0xffff < uVar7) set STATUS_FILE_CORRUPT_ERROR (0xc0000102) and ExRaiseStatus() to abort the mount. |
DriverEntry |
code change |
code (CFR feature registration linked in) | DriverEntry and the RtlRegister/RecordFeatureUsage imports were added when this build introduced Feature_930095419 CFR gating to exfat; not the vulnerable code itself. |
Feature_930095419 |
gate |
added (CFR gate) | CFR flag gating the overflow guard in FppSetupAllocationSupport; the original unchecked rounding still ships when the flag is disabled. |
Root Cause Analysis
CVE-2025-21180 — Windows exFAT File System exfat.sys Allocation-Support Size Integer Overflow → Heap Buffer Overflow (Mount-Time RCE)
Summary
| Product | Windows — exfat.sys (Windows exFAT File System driver) |
| CVE ID | CVE-2025-21180 |
| Impact | Remote Code Execution (local; “Remote” = attacker location — arbitrary code execution) |
| MSRC severity | Important |
| CVSS | 7.8 / 6.8 — CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C |
| CWE | CWE-122: Heap-based Buffer Overflow (via integer overflow) |
| Delivery | Local — user mounts a specially crafted exFAT volume (VHD) |
| KB / Fixed build | KB5053598 — exfat.sys 10.0.26100.3470 (Win11 24H2 x64) |
| Patch Date | March 11, 2025 (2025-Mar) |
| Pre-patch binary | exfat.sys 10.0.26100.2454 — SHA256 8a6a3fe8720003c9489a5baacb6d2a64e2a1bbbbbfe7187face4a44d80a6c786 |
| Post-patch binary | exfat.sys 10.0.26100.3470 — SHA256 841c4900a603398f6dcf6f6dd394a3183182a394c2fc00f1a241e2b70140df09 |
| Feature flag | Feature_930095419 — the fix is CFR-gated |
| Exploitability | Exploitation More Likely; not publicly disclosed; not exploited (per MSRC) |
Product Description
exfat.sys is the Windows exFAT file-system driver. When an exFAT volume is
mounted, FppSetupAllocationSupport derives the parameters of the volume’s
allocation-bitmap support from on-disk metadata (the exFAT boot region:
BytesPerSectorShift, SectorsPerClusterShift, cluster count, and related length
fields) and sizes the in-memory structures used to track cluster allocation.
Vulnerability Summary
FppSetupAllocationSupport takes a 32-bit count/length derived from the (untrusted)
exFAT volume (param_2 + 0x138, set from an on-disk field) and rounds it up to a
granularity boundary by adding 0xffff. Pre-patch, this count + 0xffff was computed
without an overflow check, so a crafted volume supplying a value near 0xFFFFFFFF
would wrap the 32-bit addition to a small number (CWE-190), producing an
undersized heap allocation for the allocation-support structures. Subsequent
population of those structures then writes past the short buffer — a heap-based
buffer overflow (CWE-122). Because exFAT parses the volume at mount time, an
attacker who convinces a local user to mount a malicious VHD (AV:L, UI:R) can
trigger the overflow and achieve arbitrary code execution in the kernel.
Prerequisites and Constraints
- Local; no privileges (
PR:N) but user interaction (UI:R): the victim mounts a specially crafted exFAT volume / VHD. - The crafted volume supplies an allocation count/length near
UINT_MAXso the+ 0xffffrounding overflows. - Result: an undersized allocation is made and then overrun → heap overflow at mount.
Vulnerability Details
Root Cause
The allocation-support size was rounded up with count + 0xffff using 32-bit
arithmetic on a volume-controlled count, with no check that the addition did not wrap.
A near-UINT_MAX count wrapped to a tiny size, so the allocation was too small for the
data later written into it.
The patch (confirmed — diff, .2454 → .3470)
The diff shows FppSetupAllocationSupport gaining an explicit overflow guard
(gated behind Feature_930095419) that aborts the mount when the + 0xffff rounding
would wrap:
// FppSetupAllocationSupport (10.0.26100.3470) — PATCHED (from the diff)
uVar7 = *(uint *)(param_2 + 0x138); // 32-bit count/length from the volume
if (Feature_930095419__private_IsEnabled()
&& (uVar7 + 0xffff < uVar7)) { // *** unsigned overflow check on the rounding ***
*(int *)(param_1 + 0x48) = 0xc0000102; // STATUS_FILE_CORRUPT_ERROR
ExRaiseStatus(); // abort the mount (does not return)
}
uVar7 + 0xffff < uVar7 is true only when adding 0xffff wraps the 32-bit value —
exactly the condition that previously produced the undersized allocation. On that
path the driver now records STATUS_FILE_CORRUPT_ERROR and raises, rejecting the
malformed volume before any undersized buffer is allocated or written, closing the
integer-overflow-to-heap-overflow.
Patch Completeness Assessment
CFR-gated behind Feature_930095419. The overflow guard runs only when the flag
is enabled; the original unchecked rounding still ships when disabled. Verify
Feature_930095419 is enabled to confirm the fix is live. (The diff is a wide
.2454 → .3470 span that also linked in the CFR feature-usage instrumentation; the
security-relevant code change is the overflow guard above.)
Detection Guidance
Behavioural. Pool corruption / bugcheck crashes in exfat!FppSetupAllocationSupport
(and exFAT mount paths) when mounting removable media or VHDs on unpatched/flag-disabled
builds. Treat mounting of untrusted exFAT volumes / VHDs as a risk; restrict auto-mount
of attacker-supplied disk images.
Config. The fix is CFR-gated — confirm Feature_930095419 is enabled.
References
- MSRC advisory — CVE-2025-21180 (Windows exFAT File System Remote Code Execution), released 2025-03-11, KB5053598.
- Full binary diff:
/data/patch_diffs/exfat_sys-cve-2025-21180-ghidriff.md
Attack Path
A crafted exFAT volume overflows the allocation-support size rounding, undersizing a heap buffer that is then overrun at mount
Derived from the patch delta: the checks added by the vendor identify which fields crossed a trust boundary unvalidated. Reachability and privilege are taken from the call chain in the RCA report.