CVE-2026-21242 — Windows Subsystem for Linux Elevation of Privilege Vulnerability
Executive Summary
Use after free in Windows Subsystem for Linux allows an authorized attacker to elevate privileges locally.
Overview
Verified Attribution
Binary/function confirmed from a public vendor or researcher report; this pin overrides the keyword heuristic.
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 21H2 for ARM64-based Systems | 5075912 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 10 Version 21H2 for x64-based Systems | 5075912 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 10 Version 22H2 for ARM64-based Systems | 5075912 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 10 Version 22H2 for x64-based Systems | 5075912 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 11 Version 23H2 for ARM64-based Systems | 5075941 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 11 Version 23H2 for x64-based Systems | 5075941 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 11 Version 24H2 for ARM64-based Systems 5077181 (Security Update) 5077212 (Security Hotpatch Update) Important Elevation of Privilege 5073379 Base: 7.0 Temporal: 6.1 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 10.0.26100.7840 10.0.26100.7781 Yes None Windows 11 Version 24H2 for x64-based Systems 5077212 (Security Hotpatch Update) 5077181 (Security Update) Important Elevation of Privilege 5074109 Base: 7.0 Temporal: 6.1 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 10.0.26100.7781 10.0.26100.7840 Yes None Windows 11 Version 25H2 for ARM64-based Systems 5077181 (Security Update) 5077212 (Security Hotpatch Update) Important Elevation of Privilege 5074109 Base: 7.0 Temporal: 6.1 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 10.0.26200.7840 10.0.26200.7781 Yes None Windows 11 Version 25H2 for x64-based Systems 5077181 (Security Update) 5077212 (Security Hotpatch Update) Important Elevation of Privilege 5074109 Base: 7.0 Temporal: 6.1 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 10.0.26200.7840 10.0.26200.7781 Yes None Windows 11 Version 26H1 for ARM64-based Systems | 5077179 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows 11 version 26H1 for x64-based Systems | 5077179 (Security Update) |
Important | Elevation of Privilege | Yes |
| Windows Server 2022 5075906 (Security Update) 5075943 (Security Hotpatch Update) Important Elevation of Privilege 5073457 Base: 7.0 Temporal: 6.1 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 10.0.20348.4773 10.0.20348.4711 Yes None Windows Server 2022 (Server Core installation) 5075906 (Security Update) 5075943 (Security Hotpatch Update) Important Elevation of Privilege 5073457 Base: 7.0 Temporal: 6.1 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 10.0.20348.4773 10.0.20348.4711 Yes None Windows Server 2022, 23H2 Edition (Server Core installation) | 5075897 (Security Update) |
Important | Elevation of Privilege | Yes |
Patches
| Article | Type | Restart |
|---|---|---|
5075912 |
Security Update | Yes |
5075941 |
Security Update | Yes |
5077179 |
Security Update | Yes |
5075897 |
Security Update | Yes |
Patch Diff
Use-after-free (CWE-416) in the Windows 9P/WSL redirector p9rdr.sys UserCallback timeout path, local EoP. Opening \Device\P9Rdr\wsl.localhost\... drives p9fs::P9CreateVNetRoot -> Device::CreateNetRootAndVNetRoot -> UserCallbackManager::CallUserCallback -> NotifyUserProcess, which registers a new p9fs::UserCallback and calls p9fs::UserCallback::SetCallbackTimeout to arm a timer. PRE: SetCallbackTimeout calls ExAllocateTimer (which does ExAllocatePool2(0xA0,'mTxE')); if an attacker exhausts pool so ExAllocateTimer fails, SetCallbackTimeout returns STATUS_INSUFFICIENT_RESOURCES (0xC000009A) up through NotifyUserProcess/CallUserCallback/Device::CallUserCallback, and CreateNetRootAndVNetRoot then calls rdbss!RxFinishPhysicalNetRootConstruction to free the NetRootConstructionContext while the just-registered callback still references the create RxContext/NetRoot - a use-after-free. Diff of p9rdr.sys 10.0.26100.7824 -> .8328 (Feb 10 2026, KB5077181) confirms the fix: gated behind CFR flags Feature_1655910715 / Feature_3906416953, the UserCallback registration/timeout is reworked so the callback is reference-counted and released under the manager lock (UserCallback::ReleaseReference in FindOrInsertCallbackWithLockHeld) and SetCallbackTimeout no longer leaves a dangling callback on the timer-allocation failure path, keeping the callback and the create context lifetimes in sync.
| Function | Address | Change | Note |
|---|---|---|---|
p9fs::UserCallback::SetCallbackTimeout |
code change |
code (timer-allocation failure path reworked, CFR-gated) | Pre: inline ExAllocateTimer(TimerCallback,this,0) under Feature_1655910715; on ExAllocateTimer failure returns 0xC000009A, and the caller CreateNetRootAndVNetRoot frees NetRootConstructionContext while the registered callback still references the create context -> UAF. Post: timer lifecycle reworked; the ExAllocateTimer/DeleteTimer inline block is removed and the callback is reference-released, so a timer-alloc failure no longer strands a callback over a freed context. |
p9fs::UserCallbackManager::FindOrInsertCallbackWithLockHeld |
code change |
code (reference release under lock, CFR-gated) | Now calls p9fs::UserCallback::ReleaseReference on the callback under the manager lock so the callback cannot outlive its create context. |
p9fs::UserCallbackManager::RegisterUserCallback |
code change |
code (reference management, CFR-gated) | Reworked registration path participating in the reference-counted callback lifetime. |
Feature_1655910715 / Feature_3906416953 |
gate |
added (CFR gate) | CFR flags gating the reference-counted callback/timeout lifetime; the original path still ships when disabled. |
Root Cause Analysis
CVE-2026-21242 — Windows 9P Redirector p9rdr.sys UserCallback Lifetime UAF on the SetCallbackTimeout Timer-Allocation Failure Path
Summary
| Product | Windows — p9rdr.sys (Plan 9 / 9P redirector; WSL \\wsl.localhost file access) |
| CVE ID | CVE-2026-21242 |
| 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 |
| Delivery | Local — open \Device\P9Rdr\wsl.localhost\... under kernel-pool exhaustion |
| KB / Fixed build | KB5077181 — p9rdr.sys 10.0.26100.8328 (Win11 24H2 x64) |
| Patch Date | February 10, 2026 (2026-Feb) |
| Pre-patch binary | p9rdr.sys 10.0.26100.7824 — SHA256 f52bad554e22d669e8129ce19b7eb8507bdbbd1306284e9a3afac6316bad5e97 |
| Post-patch binary | p9rdr.sys 10.0.26100.8328 — SHA256 e532c53349f770f2ba3ce7d503d7f3e24f792c09983bb5649a93b4d3c373354d |
| Feature flag | Feature_1655910715 / Feature_3906416953 — the fix is CFR-gated |
| Exploitability | Exploitation Less Likely; not publicly disclosed; not exploited (per MSRC) |
Product Description
p9rdr.sys is the Windows 9P (Plan 9) redirector used by WSL for
\\wsl.localhost\.... Opening \Device\P9Rdr\wsl.localhost\... invokes
p9fs::P9CreateVNetRoot (from rdbss!RxConstructNetRoot), which calls
p9fs::Device::CreateNetRootAndVNetRoot →
p9fs::UserCallbackManager::CallUserCallback. When no callback is registered it
calls NotifyUserProcess, which signals P9RdrService (a WNF update), creates a
p9fs::UserCallback, adds it to the manager list, and calls
p9fs::UserCallback::SetCallbackTimeout to arm a timeout:
p9rdr!p9fs::UserCallbackManager::NotifyUserProcess
p9rdr!p9fs::UserCallbackManager::CallUserCallback
p9rdr!p9fs::Device::CallUserCallback
p9rdr!p9fs::Device::CreateNetRootAndVNetRoot
p9rdr!p9fs::P9CreateVNetRoot
rdbss!RxConstructNetRoot
Vulnerability Summary
SetCallbackTimeout allocated the timer inline with ExAllocateTimer, which
internally does ExAllocatePool2(0xA0, 'mTxE'). If an attacker exhausts kernel
pool so that ExAllocateTimer fails, SetCallbackTimeout returns
STATUS_INSUFFICIENT_RESOURCES (0xC000009A). That error propagates up through
NotifyUserProcess → CallUserCallback → Device::CallUserCallback, and because
Device::CallUserCallback returns a failure, CreateNetRootAndVNetRoot calls
rdbss!RxFinishPhysicalNetRootConstruction to free the NetRootConstructionContext.
But the UserCallback that was already registered (added to the manager list, and
referencing the create RxContext/NetRoot) is not torn down on this failure path,
so it now points at freed construction state — a use-after-free (CWE-416). The
redirector runs in the kernel and the open path is reachable by a low-privileged
local user (the reporter reaches it from WSL), making the freed-object reuse a
local EoP primitive; AC:H reflects the need to reliably force the allocation
failure.
Prerequisites and Constraints
- Local, low-privileged (
PR:L,AV:L);AC:H— the attacker must driveExAllocateTimerto fail (kernel-pool exhaustion) at the moment a WSL create is registering its user callback. - Open
\Device\P9Rdr\wsl.localhost\...to reachNotifyUserProcess→SetCallbackTimeout. - Result: the create context is freed while the registered callback still references it.
Vulnerability Details
Root Cause
On the SetCallbackTimeout timer-allocation failure path, the already-registered
UserCallback (and its reference to the create context) was not released before
CreateNetRootAndVNetRoot freed the NetRootConstructionContext, leaving a
dangling reference.
The patch (confirmed — diff, .7824 → .8328)
Gated behind Feature_1655910715 / Feature_3906416953, the UserCallback
registration and timeout are reworked so the callback is reference-counted and
released under the manager lock, and SetCallbackTimeout no longer performs the
failure-prone inline ExAllocateTimer/DeleteTimer that could strand a callback:
// p9fs::UserCallback::SetCallbackTimeout (.7824) — PRE (removed in the fix):
// uVar3 = Feature_1655910715__private_IsEnabledDeviceUsageNoInline();
// lVar4 = ExAllocateTimer(TimerCallback, this, 0);
// if (this->Timer != NULL) details::DeleteTimer(this->Timer); // failure could strand the callback
// post: timer lifecycle reworked; ExAllocateTimer/DeleteTimer inline block removed
//
// p9fs::UserCallbackManager::FindOrInsertCallbackWithLockHeld (.8328) — PATCHED:
UserCallback::ReleaseReference(callback); // release under the manager lock
By reference-counting the callback and releasing it under the lock (and removing the strand-prone inline timer allocation), a timer-allocation failure no longer leaves a callback referencing a freed construction context, closing the UAF.
Patch Completeness Assessment
CFR-gated behind Feature_1655910715 / Feature_3906416953. The
reference-managed path runs only when the flags are enabled; the original path
still ships when disabled. Verify the flags are enabled to confirm the fix is live.
Detection Guidance
Behavioural. Repeated \\wsl.localhost\... / \Device\P9Rdr\... opens under
deliberate kernel-pool pressure (forcing 'mTxE' timer allocations to fail); UAF /
pool-corruption bugchecks in p9rdr!p9fs::UserCallbackManager::* /
NotifyUserProcess on unpatched/flag-disabled builds.
Config. The fix is CFR-gated — confirm Feature_1655910715 /
Feature_3906416953 are enabled.
References
- MSRC advisory — CVE-2026-21242 (Windows 9P / WSL Redirector Elevation of Privilege), released 2026-02-10, KB5077181.
- Full binary diff:
/data/patch_diffs/p9rdr_sys-cve-2026-21242-ghidriff.md - Related same-KB p9rdr UserCallback lifetime UAF: CVE-2026-21237.
Attack Path
A timer-allocation failure on the WSL create path frees the NetRoot construction context while a registered user callback still references it
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
ChenJian with Sea Security Orca Team