CVE-2026-40380 — Windows Volume Manager Extension Driver Remote Code Execution Vulnerability
Executive Summary
Heap-based buffer overflow in Volume Manager Extension Driver allows an authorized attacker to execute code with a physical attack.
Overview
CVSS Vector
CVSS:3.1/AV:P/AC:L/PR:H/UI:N/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 Version 1607 for 32-bit Systems | 5087537 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 1607 for x64-based Systems | 5087537 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 1809 for 32-bit Systems | 5087538 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 1809 for x64-based Systems | 5087538 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 21H2 for 32-bit Systems | 5087544 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 21H2 for ARM64-based Systems | 5087544 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 21H2 for x64-based Systems | 5087544 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 22H2 for 32-bit Systems | 5094127 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 22H2 for ARM64-based Systems | 5094127 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 10 Version 22H2 for x64-based Systems | 5094127 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 11 Version 23H2 for ARM64-based Systems | 5087420 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 11 Version 23H2 for x64-based Systems | 5093998 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 11 Version 24H2 for ARM64-based Systems 5089549 (Security Update) 5089466 (Security Hotpatch Update) Important Remote Code Execution 5082063 Base: 6.2 Temporal: 5.4 Vector: CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 10.0.26100.8457 10.0.26100.8390 Yes None Windows 11 Version 24H2 for x64-based Systems 5089549 (Security Update) 5089466 (Security Hotpatch Update) Important Remote Code Execution 5082063 Base: 6.2 Temporal: 5.4 Vector: CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 10.0.26100.8457 10.0.26100.8390 Yes None Windows 11 Version 25H2 for ARM64-based Systems 5089549 (Security Update) 5089466 (Security Hotpatch Update) Important Remote Code Execution 5083769 Base: 6.2 Temporal: 5.4 Vector: CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 10.0.26200.8457 10.0.26200.8390 Yes None Windows 11 Version 25H2 for x64-based Systems 5089549 (Security Update) 5089466 (Security Hotpatch Update) Important Remote Code Execution 5083769 Base: 6.2 Temporal: 5.4 Vector: CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 10.0.26200.8457 10.0.26200.8390 Yes None Windows 11 Version 26H1 for ARM64-based Systems | 5089548 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows 11 version 26H1 for x64-based Systems | 5089548 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows Server 2012 | 5087470 (Monthly Rollup) |
Important | Remote Code Execution | Yes |
| Windows Server 2012 (Server Core installation) | 5087470 (Monthly Rollup) |
Important | Remote Code Execution | Yes |
| Windows Server 2012 R2 | 5087471 (Monthly Rollup) |
Important | Remote Code Execution | Yes |
| Windows Server 2012 R2 (Server Core installation) | 5087471 (Monthly Rollup) |
Important | Remote Code Execution | Yes |
| Windows Server 2016 | 5087537 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows Server 2016 (Server Core installation) | 5087537 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows Server 2019 | 5087538 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows Server 2019 (Server Core installation) | 5087538 (Security Update) |
Important | Remote Code Execution | Yes |
| Windows Server 2022 5087545 (Security Update) 5087424 (Security Hotpatch Update) Important Remote Code Execution 5082142 Base: 6.2 Temporal: 5.4 Vector: CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 10.0.20348.5139 10.0.20348.5074 Yes None Windows Server 2022 (Server Core installation) 5087545 (Security Update) 5087424 (Security Hotpatch Update) Important Remote Code Execution 5082142 Base: 6.2 Temporal: 5.4 Vector: CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C 10.0.20348.5139 10.0.20348.5074 Yes None Windows Server 2022, 23H2 Edition (Server Core installation) | 5087541 (Security Update) |
Important | Remote Code Execution | Yes |
Patches
| Article | Type | Restart |
|---|---|---|
5087537 |
Security Update | Yes |
5087538 |
Security Update | Yes |
5087544 |
Security Update | Yes |
5094127 |
Security Update | Yes |
5087420 |
Security Update | Yes |
5093998 |
Security Update | Yes |
5089548 |
Security Update | Yes |
5087470 |
Monthly Rollup | Yes |
5087471 |
Monthly Rollup | Yes |
5087541 |
Security Update | Yes |
Patch Diff
Integer-truncation memory corruption (CWE-197 -> CWE-122 heap overflow / CWE-125 OOB read) in the Windows Volume Manager Extension driver volmgrx.sys VHD/VHDX metadata parser, RCE via a crafted virtual-disk image (AV:P). 64-bit QWORD metadata (sector numbers, offsets, sizes) read from the disk image is consumed by 32-bit code without range validation, so the low-32-bit value used for (e.g.) bitmap validation diverges from the full 64-bit value used in comparisons/memory operations. In VMX_DISK_HEADER::Unformat the seven 64-bit header fields (total sector count, TOC sector pair, log/config sectors, two extension offsets) were not checked against 0xFFFFFFFF before use in 32-bit ops. In VMX_PHYSICAL_DISK::ReadToc a TOC entry's offset (QWORD idx 5) and size (QWORD idx 6) are read as QWORDs but bitmap-validated using only the low 32 bits (e.g. 0x1_0000_0001 validates as 1), so during TOC parsing an OOB read/write past the bitmap boundary can corrupt adjacent kernel pool. IN-HOUSE ghidriff of volmgrx.sys 10.0.26100.1150 -> .8457 (May 12 2026, KB5089549) confirms the fix: Unformat adds seven `field < 0x100000000` checks; ReadToc adds `offset > 0xFFFFFFFF || size > 0xFFFFFFFF || offset+size > 0xFFFFFFFF` and breaks the parse loop (cleaning up the TOC buffer); both gated behind CFR flag Feature_3984574778. Note: our x64 24H2 diff shows Feature_3984574778, differing from the circulated screenshots' Feature_4253010234 (build/arch difference); the > 0xFFFFFFFF bounds are identical. We ship what our diff shows.
| Function | Address | Change | Note |
|---|---|---|---|
VMX_DISK_HEADER::Unformat |
code change |
code (seven 64-bit header-field upper-bound checks, CFR-gated) | Post (Feature_3984574778 enabled): accepts the header only if all seven 64-bit fields are < 0x100000000 - fields at this+0x18, +0x20, +0xa0, +0xa8, +0xb0, +0xc0, +0xc8 (total sector count, TOC sector pair, log/config sectors, two extension offsets). Pre: no such upper-bound check before the values feed 32-bit calculations/fields. |
VMX_PHYSICAL_DISK::ReadToc |
code change |
code (TOC offset/size/sum overflow check, CFR-gated) | Post (Feature_3984574778 enabled): per TOC entry, break the parse loop if offset (*(u64*)(entry+0x28), QWORD idx 5) > 0xFFFFFFFF, or size (*(u64*)(entry+0x30), QWORD idx 6) > 0xFFFFFFFF, or offset+size > 0xFFFFFFFF, then clean up the TOC buffer. Pre: only the low 32 bits were used for bitmap validation while the 64-bit value drove the access -> truncation mismatch -> OOB. |
Feature_3984574778 |
new flag |
added (CFR gate) | New CFR flag introduced by this patch gating both the Unformat and ReadToc range checks; the original unchecked parsing still ships in .8457. |
Root Cause Analysis
CVE-2026-40380 — Windows Volume Manager Extension volmgrx.sys Integer Truncation in VHD/VHDX Metadata Parsing (VMX_DISK_HEADER::Unformat / VMX_PHYSICAL_DISK::ReadToc)
Summary
| Product | Windows — volmgrx.sys (Volume Manager Extension driver; VHD/VHDX metadata parsing) |
| CVE ID | CVE-2026-40380 |
| Impact | Remote Code Execution |
| MSRC severity | Important |
| CVSS | 6.2 / 5.4 — CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C |
| CWE | CWE-122 Heap-based Buffer Overflow; CWE-197 Numeric Truncation Error; CWE-125 Out-of-bounds Read |
| Delivery | A crafted VHD/VHDX virtual-disk image parsed by the driver (AV:P) |
| KB / Fixed build | KB5089549 — volmgrx.sys 10.0.26100.8457 (Win11 24H2 x64) |
| Patch Date | May 12, 2026 (2026-May) |
| Pre-patch binary | volmgrx.sys 10.0.26100.1150 — SHA256 7c0d3f68af9297c167d64c53a31f6dd3dfd01861cdd3fafd6e545ff1bd3eceaa |
| Post-patch binary | volmgrx.sys 10.0.26100.8457 — SHA256 8ad69577e078b5d605a7e9d814df34b8bb049715fc3656eb043d9319b977c864 |
| Feature flag | Feature_3984574778 — the fix is CFR-gated |
| Exploitability | Exploitation Less Likely; not publicly disclosed; not exploited (per MSRC) |
Product Description
volmgrx.sys is the Windows Volume Manager Extension (dynamic-disk) driver. It
parses VHD/VHDX virtual-disk metadata — the disk header and its table of
contents (TOC) — in kernel. Fields such as sector counts, offsets and sizes are
stored on disk as 64-bit QWORDs. Because a crafted disk image can drive this
kernel parser, a size-handling flaw is a code-execution vector (physical/AV:P:
the malicious image must be attached/mounted).
Vulnerability Summary
The core defect is integer truncation (CWE-197): 64-bit metadata values read from the disk image are used in 32-bit operations without range validation, so a value’s low 32 bits are used for one purpose (e.g. bitmap validation) while the full 64-bit value is used for another (comparison / memory operation), producing a semantic mismatch between the value that was validated and the value that drives the actual access.
VMX_DISK_HEADER::Unformat — the total sector count, the TOC sector pair, the
log/configuration sectors and two extension offsets (seven 64-bit header fields)
were not checked against 0xFFFFFFFF before being passed into subsequent
32-bit calculations/fields.
VMX_PHYSICAL_DISK::ReadToc — a TOC entry’s offset (*((QWORD*)entry + 5))
and size (*((QWORD*)entry + 6)) are read as QWORDs, but bitmap validation uses
only the low 32 bits. A crafted entry with e.g. 0x1_0000_0001 is validated as
1 yet processed with the original 64-bit value, so validation and use diverge.
Combined, a crafted VHD/VHDX can induce truncation and a size-validation mismatch; during TOC parsing a read or write can land outside the bitmap boundary, corrupting adjacent kernel pool structures (CWE-122 / CWE-125).
Prerequisites and Constraints
AV:P/PR:H: an attacker gets the driver to parse a crafted VHD/VHDX image (attach/mount). No user interaction beyond that.- Trigger: header fields or TOC offset/size set so the low 32 bits pass validation while the full 64-bit value drives the memory operation.
- Result is out-of-bounds kernel access / pool corruption → potential RCE.
Vulnerability Details
Root Cause
64-bit disk metadata (sector numbers, offsets, sizes) is consumed by 32-bit code paths without first verifying it fits in 32 bits, so truncation lets the value used for bounds validation differ from the value used for the actual access.
The patch (confirmed — diff, .1150 → .8457)
Gated behind Feature_3984574778, both functions add explicit upper-bound and
summation-overflow checks before the 64-bit values are used as 32-bit.
VMX_DISK_HEADER::Unformat — seven header fields must each be < 0x100000000:
// VMX_DISK_HEADER::Unformat (10.0.26100.8457) — PATCHED, feature-enabled branch
if ( Feature_3984574778__private_IsEnabledDeviceUsageNoInline() == 0
|| ( *(u64*)(this+0xa0) < 0x100000000 && *(u64*)(this+0x18) < 0x100000000
&& *(u64*)(this+0x20) < 0x100000000 && *(u64*)(this+0xa8) < 0x100000000
&& *(u64*)(this+0xb0) < 0x100000000 && *(u64*)(this+0xc0) < 0x100000000
&& *(u64*)(this+0xc8) < 0x100000000 ) )
{ *param_1 = ...; return 0; } // accept only when every 64-bit field fits in 32 bits
VMX_PHYSICAL_DISK::ReadToc — per TOC entry, reject when offset or size exceeds
0xFFFFFFFF, or when their sum overflows 32 bits, and break out of the
parsing loop (the TOC buffer/objects are then cleaned up):
// VMX_PHYSICAL_DISK::ReadToc (10.0.26100.8457) — PATCHED, feature-enabled branch
if ( Feature_3984574778__private_IsEnabledDeviceUsageNoInline()
&& ( 0xffffffff < *(u64*)(entry+0x28) // offset > 0xFFFFFFFF
|| 0xffffffff < *(u64*)(entry+0x30) // size > 0xFFFFFFFF
|| 0xffffffff < *(u64*)(entry+0x30) + *(u64*)(entry+0x28) ) ) // offset+size overflow
{ break; } // stop trusting this TOC entry
Entry offset +0x28 and size +0x30 correspond to QWORD indices 5 and 6 —
exactly the v49/v48 fields in the public analysis. If the check fails the loop
exits before any access based on the invalid values.
Patch Completeness Assessment
CFR-gated behind Feature_3984574778. The checks run only when the flag is
enabled; the original unchecked parsing still ships in .8457. Patch state is not
determined by file version alone — the runtime-gated pattern seen across this
corpus. Verify Feature_3984574778 is enabled to confirm the bounds are live.
Detection Guidance
Behavioural. Attaching/mounting untrusted VHD/VHDX images; disk headers or
TOC entries whose 64-bit sector/offset/size fields exceed 0xFFFFFFFF.
Crash signature. Kernel pool corruption / out-of-bounds access in
volmgrx!VMX_PHYSICAL_DISK::ReadToc or VMX_DISK_HEADER::Unformat while parsing
a virtual disk on unpatched/flag-disabled builds.
Config. The fix is CFR-gated — confirm Feature_3984574778 is enabled so the
> 0xFFFFFFFF bounds are active.
References
- MSRC advisory — CVE-2026-40380 (Windows Volume Manager Extension Driver Remote Code Execution), released 2026-05-12, KB5089549.
- Full binary diff:
/data/patch_diffs/volmgrx_sys-cve-2026-40380-ghidriff.md
Attack Path
A crafted VHD/VHDX supplies 64-bit metadata whose low 32 bits pass validation but whose full value drives an out-of-bounds kernel access
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.
Exploits & PoC
Detection Rules
Acknowledgments
Calif.io in collaboration with Claude and Anthropic Research