Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2025-24983: Windows Win32 Kernel Subsystem Use-After-Free Privilege Escalation

Published Mar 11, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.0High · v3.1
EPSS2.4%84th percentile
CISA KEVYesAdded Mar 11, 2025
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2025-24983CWE-416 · Use After Free

CVE-2025-24983 is a use-after-free vulnerability in the Windows Win32 Kernel Subsystem that allows a locally authenticated, low-privileged attacker to elevate privileges to SYSTEM. Successful exploitation requires winning a race condition but does not require user interaction. The vulnerability has been actively exploited, including in campaigns involving the PipeMagic backdoor and ransomware.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation grants SYSTEM privileges on the affected Windows system, potentially compromising its confidentiality, integrity, and availability. The vulnerability has been used with the PipeMagic backdoor to facilitate ransomware deployment.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by limiting local access to trusted users and administrators only, minimizing opportunities for attackers to obtain or retain low-privilege execution on endpoints, and prioritizing monitoring for post-compromise privilege-escalation activity on vulnerable Windows systems. Because exploitation is local and requires prior authenticated access, controls that prevent initial compromise and restrict interactive or code-execution access can reduce risk until patches are applied.

Remediation

Patch, then assume compromise.

Apply the applicable Microsoft March 2025 security update for each affected Windows system. Prioritize deployment because exploitation has been detected. Specific update packages, KB numbers, and fixed versions are not available in the supplied information.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2025-24983-1DayThis standalone C++ repository implements a build-specific local privilege-escalation exploit for CVE-2025-24983. Its 40 listed files comprise two C++ programs, a batch build script, root documentation, and a phnt directory containing 33 Native API headers plus CMake metadata, documentation, and an MIT license. PoC.cpp supplies supervisor, attempt, and shell-helper modes. Its visible code dynamically resolves Win32k/DirectComposition syscalls and leaks kernel object addresses through NtQuerySystemInformation. The supervisor monitors success, anomaly, and child-exit events with a 180-second timeout. The documented exploit races WaitForInputIdle against victim GUI initialization and teardown, freeing a W32PROCESS while a stale thread-lock pointer remains. Controlled DirectComposition allocations reclaim the freed memory, allowing stale cleanup to affect a helper thread's PreviousMode. The README describes subsequent kernel read/write, SYSTEM-token acquisition, restoration of PreviousMode, and launch of a SYSTEM command prompt. The fully visible victim.cpp supports this strategy through inherited shared-memory/event handles, two CPU-affinitized workers, delayed NtUserGetThreadState calls, and virtual-address reservations intended to prevent a GDI-section mapping. It deliberately resolves the syscall without importing USER32/GDI32. No runtime network communication, remote callback, persistence mechanism, or exfiltration is evident in the supplied excerpts. Network device paths and documentation URLs in PHNT headers are library definitions/references, not evidence that the exploit contacts those endpoints. This is exploit code rather than a detector, with no clear indication of a fake exploit. However, PoC.cpp is substantially truncated, so the central corruption and payload stages cannot be fully audited. The listed PHNT tree also lacks headers directly included by phnt.h, such as ntexapi.h and ntpsapi.h, so compilation from this inventory alone is likely to fail. The README references a PDF absent from the inventory. The repository URL is inferred from its demonstration link; no analyzed Git reference or archive size was supplied, represented by an empty ref and size_bytes of 0.sote-CJ · Disclosed Nov 19, 2026 · cpp · c · localOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2008 R2operating_system
Microsoft CorporationWindows Server 2008 Sp2operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
FAQ

Frequently asked questions

Is CVE-2025-24983 exploited in the wild?
Yes. As of Oct 10, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 11, 2025.
Is there a public exploit for CVE-2025-24983?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2025-24983, the earliest disclosed Nov 19, 2026.
Is there a patch for CVE-2025-24983?
Apply the applicable Microsoft March 2025 security update for each affected Windows system. Prioritize deployment because exploitation has been detected.
What products are affected by CVE-2025-24983?
Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows Server 2008, Microsoft Corporation Windows Server 2008 R2, Microsoft Corporation Windows Server 2008 Sp2, and 3 more.
How severe is CVE-2025-24983?
CVE-2025-24983 has a CVSS v3.1 score of 7.0 (High) and an EPSS score of 2.4% (84th percentile) as of Oct 10, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.