CVE-2022-24521: Windows CLFS Driver Local Privilege Escalation
- Vendor
- Microsoft Corporation
CVE-2022-24521 is a local privilege-escalation vulnerability in the Microsoft Windows Common Log File System (CLFS) driver. Insufficient validation of crafted base-log metadata permits overlapping structures to corrupt a container-object pointer. One demonstrated exploitation path abuses CClfsBaseFilePersisted::LoadContainerQ and signature encoding/decoding to restore an attacker-controlled pContainer pointer, enabling control of an indirect kernel call. Another observed exploit overlaps client and container contexts to obtain an arbitrary kernel-memory decrement. These primitives can support process-token replacement and escalation to SYSTEM. The vulnerability affected Windows desktop and server releases and was exploited in the wild before its April 2022 patch.
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.
A low-privileged local attacker can gain SYSTEM privileges through kernel-memory manipulation and process-token replacement. Demonstrated techniques provide kernel-memory reads and writes or indirect kernel-call control. Exploitation has been observed in ransomware operations, including Cuba and Nokoyawa, as a post-compromise privilege-escalation step.
Mitigation
If you can’t patch tonight, do this now.
Newer Windows 11 builds restrict kernel-address disclosure and PreviousMode manipulation used by demonstrated exploitation techniques; these restrictions are not a substitute for the security update. Monitor low- or medium-integrity CLFS log manipulation followed by SYSTEM-level activity, suspicious integrity-level transitions, and user-mode access to kernel-memory addresses. No vulnerability-specific workaround is identified.
Remediation
Patch, then assume compromise.
Apply the applicable Microsoft security update released on April 12, 2022, or a superseding update that includes the fix for CVE-2022-24521. The patch adds validation of context offsets, prevents overlap with signature data, and validates context fields. Specific update package identifiers and fixed build numbers are not available here.
Exploits
1 exploit validated by Mallory's analysis.
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.
Frequently asked questions
- Is CVE-2022-24521 exploited in the wild?
- Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Apr 13, 2022.
- Is there a public exploit for CVE-2022-24521?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2022-24521, the earliest disclosed Feb 19, 2026.
- Is there a patch for CVE-2022-24521?
- Apply the applicable Microsoft security update released on April 12, 2022, or a superseding update that includes the fix for CVE-2022-24521. The patch adds validation of context offsets, prevents overlap with signature data, and validates context fields.
- What products are affected by CVE-2022-24521?
- Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 1909, Microsoft Corporation Windows 10 20h2, and at least 15 more.
- How severe is CVE-2022-24521?
- CVE-2022-24521 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 7.1% (94th percentile) as of Oct 16, 2026.
Recent activity
19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.