CVE-2026-32070 — Windows Common Log File System Driver Elevation of Privilege Vulnerability
Executive Summary
Use after free in Windows Common Log File System Driver allows an authorized attacker to elevate privileges locally.
Overview
CVSS Vector
CVSS:3.1/AV:L/AC:H/PR:L/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 | 5082198 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 10 Version 1607 for x64-based Systems | 5082198 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 10 Version 1809 for 32-bit Systems | 5082123 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 10 Version 1809 for x64-based Systems | 5082123 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 10 Version 21H2 for 32-bit Systems | 5082200 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 10 Version 21H2 for ARM64-based Systems | 5082200 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 10 Version 21H2 for x64-based Systems | 5082200 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 10 Version 22H2 for 32-bit Systems | 5082200 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 10 Version 22H2 for ARM64-based Systems | 5082200 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 10 Version 22H2 for x64-based Systems | 5082200 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 11 Version 23H2 for ARM64-based Systems | 5082052 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 11 Version 23H2 for x64-based Systems | 5082052 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 11 Version 24H2 for ARM64-based Systems | 5083769 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 11 Version 24H2 for x64-based Systems | 5083769 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 11 Version 25H2 for ARM64-based Systems | 5083769 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 11 Version 25H2 for x64-based Systems | 5083769 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 11 Version 26H1 for ARM64-based Systems | 5083768 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 11 version 26H1 for x64-based Systems | 5083768 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows Server 2012 | 5082127 (Monthly Rollup) |
Important | Elevation of Privilege | Yes |
| Windows Server 2012 (Server Core installation) | 5082127 (Monthly Rollup) |
Important | Elevation of Privilege | Yes |
| Windows Server 2012 R2 | 5082126 (Monthly Rollup) |
Important | Elevation of Privilege | Yes |
| Windows Server 2012 R2 (Server Core installation) | 5082126 (Monthly Rollup) |
Important | Elevation of Privilege | Yes |
| Windows Server 2016 | 5082198 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows Server 2016 (Server Core installation) | 5082198 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows Server 2019 | 5082123 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows Server 2019 (Server Core installation) | 5082123 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows Server 2022 | 5082142 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows Server 2022 (Server Core installation) | 5082142 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows Server 2022, 23H2 Edition (Server Core installation) | 5082060 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows Server 2025 | 5082063 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows Server 2025 (Server Core installation) | 5082063 (Security Update) |
Important | Elevation of Privilege | Yes |
Patches
| Article | Type | Restart |
|---|---|---|
5082198 |
Security Update | Yes |
5082123 |
Security Update | Yes |
5082200 |
Security Update | Yes |
5082052 |
Security Update | Yes |
5083769 |
Security Update | Yes |
5083768 |
Security Update | Yes |
5082127 |
Monthly Rollup | Yes |
5082126 |
Monthly Rollup | Yes |
5082142 |
Security Update | Yes |
5082060 |
Security Update | Yes |
5082063 |
Security Update | Yes |
Patch Diff
Reference-count lifetime-inversion use-after-free (CWE-416) in the Windows CLFS driver clfs.sys CClfsManagedLog::AddNewClient. The function creates a COM-style reference-counted CClfsManagedLogClient, and pre-patch did: allocate + store in *a5, call Initialize (vtable+32) which registers the object EXTERNALLY (kernel structures / observer chains, e.g. InstallLogObserver), then finally AddRef (vtable+0). Because the object is published before any reference is held, its refcount is still 0 when other threads can find it; a concurrent Release drops the count below zero and frees the object, and the original thread's later AddRef touches freed memory -> UAF. The failure path also called the destructor directly (vtable+80, bFinal=1) rather than Release, which only balances the pre-patch ordering. Diff of clfs.sys 10.0.26100.8115 -> .8246 (Apr 14 2026, KB5083769) confirms AddNewClient is the changed function and gains a new CFR gate: gated behind Feature_1664551224, AddRef is moved BEFORE Initialize, and the failure path now calls Release (vtable+8) to balance the earlier AddRef; the list-insertion check became an explicit guard (if (*v18 != i) __fastfail(3u)) and control flow consolidated to a single LABEL_31 exit so the managed-log mutex is released once. All managed-log clients (CreateLogFile) reach this path. Note: our diff shows Feature_1664551224, differing from the circulated screenshots' Feature_1932986680 (build/arch difference); the AddRef-before-Initialize reorder is identical.
| Function | Address | Change | Note |
|---|---|---|---|
CClfsManagedLog::AddNewClient |
code change |
code (AddRef reordered before Initialize; Release on failure; CFR-gated) | Pre: alloc -> Initialize(vtable+32, registers externally) -> AddRef(vtable+0); refcount 0 during external exposure -> concurrent Release frees object -> later AddRef is UAF; failure path called destructor directly (vtable+80,bFinal=1). Post (Feature_1664551224 enabled): AddRef(vtable+0) first, then Initialize; on failure Release(vtable+8) to balance; list-insert guard `if (*v18 != i) __fastfail(3u)`; single LABEL_31 exit (mutex released once). |
Feature_1664551224 |
gate |
added (CFR gate) | CFR flag gating the AddRef-first ordering + Release-on-failure fix; the original ordering still ships when disabled. |
Root Cause Analysis
CVE-2026-32070 — Windows CLFS clfs.sys Reference-Count Inversion in CClfsManagedLog::AddNewClient → Use-After-Free
Summary
| Product | Windows — clfs.sys (Common Log File System driver; managed-log client) |
| CVE ID | CVE-2026-32070 |
| Impact | Elevation of Privilege |
| MSRC severity | Important |
| CVSS | 7.0 / 6.1 — CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C |
| CWE | CWE-416: Use After Free (reference-count lifetime inversion) |
| Delivery | Local race — a second thread Releases the client during registration |
| KB / Fixed build | KB5083769 — clfs.sys 10.0.26100.8246 (Win11 24H2 x64) |
| Patch Date | April 14, 2026 (2026-Apr) |
| Pre-patch binary | clfs.sys 10.0.26100.8115 — SHA256 1e0744c8e88853a05b07635daf5eadccd381658e28c2703316decb7e58e90bc9 |
| Post-patch binary | clfs.sys 10.0.26100.8246 — SHA256 d7e779b93dc05dcbc745b1ad100637b0376c29ffdff90ccad4e4fc69dcb932df |
| Feature flag | Feature_1664551224 — the fix is CFR-gated |
| Exploitability | Exploitation Less Likely; not publicly disclosed; not exploited (per MSRC) |
Product Description
clfs.sys is the Windows Common Log File System driver — a long-standing local
privilege-escalation target. CClfsManagedLog::AddNewClient creates a new
CClfsManagedLogClient (a COM-style reference-counted object), initializes it,
and takes a reference on it. All managed-log clients — reachable via
CreateLogFile and related APIs — go through this path.
Vulnerability Summary
AddNewClient performed the object’s setup in the wrong order:
- allocate the
CClfsManagedLogClientand store it in*a5, - call
Initialize(vtable+32) — which registers the object externally (kernel structures / observer/callback chains, e.g.InstallLogObserver), - only then
AddRef(vtable+0).
Because Initialize publishes the object to externally reachable locations
before any reference is taken, the reference count is still 0 at the
moment other threads can find it. If another thread discovers the registered
client and calls Release, the count goes below zero and the object is freed;
when the original thread finally reaches AddRef, it touches freed memory — a
lifetime-inversion use-after-free (CWE-416).
The failure path compounded it: on Initialize failure the pre-patch code
destroyed the object by calling its destructor directly (vtable+80, bFinal=1)
rather than Release — correct only under the “no reference taken yet” ordering.
Prerequisites and Constraints
- Local, low-privileged (
PR:L,AV:L);AC:Hreflects the narrow race window. - Race: a concurrent thread
Releases the just-registered client between its external registration (Initialize) and the original thread’sAddRef. - CLFS managed-log clients are broadly reachable (
CreateLogFile), so the path is readily triggerable.
Vulnerability Details
Root Cause
The object was made externally discoverable before a reference was held, so a
concurrent Release could drop the count below zero and free the object while
AddNewClient still intended to use it (reference-count inversion → UAF).
The patch (confirmed — diff, .8115 → .8246)
Gated behind Feature_1664551224, AddNewClient is reordered to AddRef first,
then Initialize, so a reference is already held by the time the object is
registered externally; the failure path is correspondingly changed to call the
standard Release (vtable+8) instead of the direct destructor, balancing the
earlier AddRef:
// CClfsManagedLog::AddNewClient (10.0.26100.8246) — PATCHED, feature-enabled branch
if (Feature_1664551224__private_IsEnabledDeviceUsage()) {
(*v13)(); // *** AddRef FIRST (ref held before exposure) ***
v11 = (*(*a5 + 32))(*a5, a2, a3, this); // Initialize (registers externally)
if (v11 < 0) {
(*(*a5 + 8))(*a5); // *** Release on failure (balances AddRef) ***
*a5 = 0;
goto LABEL_31;
}
}
The list-insertion integrity check was also tightened from a fall-through to an
explicit guard (if (*v18 != i) __fastfail(3u)), and control flow consolidated to
a single exit (LABEL_31) so the managed-log mutex is released in exactly one
place. Our diff of clfs.sys 10.0.26100.8115 → .8246 confirms AddNewClient is the
changed function and gains the Feature_1664551224 gate at the April KB5083769.
Patch Completeness Assessment
CFR-gated behind Feature_1664551224. The reordered AddRef-first path runs only
when the flag is enabled; the original ordering still ships when disabled. Verify
Feature_1664551224 is enabled to confirm the fix is live.
Detection Guidance
Behavioural. Concurrent CreateLogFile / managed-log client create+release
churn; UAF / low-ref bugchecks in clfs!CClfsManagedLog::AddNewClient /
CClfsManagedLogClient teardown on unpatched/flag-disabled builds.
Config. The fix is CFR-gated — confirm Feature_1664551224 is enabled.
References
- MSRC advisory — CVE-2026-32070 (Windows Common Log File System Driver Elevation of Privilege), released 2026-04-14, KB5083769.
- Full binary diff:
/data/patch_diffs/clfs_sys-cve-2026-32070-ghidriff.md
Attack Path
AddNewClient registers a CLFS managed-log client externally before taking a reference, so a racing Release frees it under the creating thread
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.