Skip to content
Server Security Center
KEVhigh7.8 Used in ransomware campaigns

CVE-2025-29824: Microsoft Windows Common Log File System (CLFS) Driver Use-After-Free

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2025-04-08.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
19%
higher than 97.4% of all CVEs
Added to CISA KEV
2025-04-08
US federal due date 2025-04-29
Automatable (CISA SSVC)
no
technical impact: total

CVE-2025-29824 explained

CVE-2025-29824 is a use-after-free flaw in the Windows Common Log File System (CLFS) driver. It lets an attacker who already has local access raise their privileges on the system. CISA lists it as known exploited, including in ransomware campaigns, so unpatched Windows clients and servers face real risk.

Impact

An attacker with low-privileged local access can elevate privileges without user interaction. The CVSS ratings show high impact on confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected system. CISA rates it as not automatable, so each attack needs manual steps. Attackers are known to exploit it, and CISA notes known ransomware use. It is typically valuable after an initial foothold has been gained.

Who is affected

The CVE record lists Windows 10 Versions 1507, 1607, 1809, 21H2 and 22H2, Windows 11 versions 22H2, 22H3, 23H2 and 24H2, Windows Server 2008 R2 Service Pack 1 (including Server Core) and Windows Server 2008 Service Pack 2. Fixed builds include 10.0.19045.5737 (Windows 10 22H2), 10.0.22631.5189 (Windows 11 23H2), 10.0.26100.3775 (Windows 11 24H2) and 6.1.7601.27670 (Server 2008 R2 SP1). More products appear in the full list on this page.

Written with AI from the data on this page and checked against it automatically.

Official description

Use after free in Windows Common Log File System Driver allows an authorized attacker to elevate privileges locally.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.20978
    Fixed in
    • 10.0.10240.20978
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.7969
    Fixed in
    • 10.0.14393.7969
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.7136
    Fixed in
    • 10.0.17763.7136
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.5737
    Fixed in
    • 10.0.19044.5737
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.5737
    Fixed in
    • 10.0.19045.5737
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.5189
    Fixed in
    • 10.0.22621.5189
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.5189
    Fixed in
    • 10.0.22631.5189
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.5189
    Fixed in
    • 10.0.22631.5189
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.3775
    Fixed in
    • 10.0.26100.3775
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.27670
    Fixed in
    • 6.1.7601.27670
Show 15 more products
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.27670
    Fixed in
    • 6.1.7601.27670
  • Microsoft Windows Server 2008 Service Pack 232-bit, x64
    Affected
    • < 6.0.6003.23220
    Fixed in
    • 6.0.6003.23220
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64
    Affected
    • < 6.0.6003.23220
    Fixed in
    • 6.0.6003.23220
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25423
    Fixed in
    • 6.2.9200.25423
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25423
    Fixed in
    • 6.2.9200.25423
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22523
    Fixed in
    • 6.3.9600.22523
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22523
    Fixed in
    • 6.3.9600.22523
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.7969
    Fixed in
    • 10.0.14393.7969
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.7969
    Fixed in
    • 10.0.14393.7969
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.7136
    Fixed in
    • 10.0.17763.7136
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.7136
    Fixed in
    • 10.0.17763.7136
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.3453
    Fixed in
    • 10.0.20348.3453
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1551
    Fixed in
    • 10.0.25398.1551
  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.3775
    Fixed in
    • 10.0.26100.3775
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.3775
    Fixed in
    • 10.0.26100.3775

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.20978
    • Microsoft Windows 10 Version 1607: 10.0.14393.7969
    • Microsoft Windows 10 Version 1809: 10.0.17763.7136
    • Microsoft Windows 10 Version 21H2: 10.0.19044.5737
    • Microsoft Windows 10 Version 22H2: 10.0.19045.5737
    • Microsoft Windows 11 version 22H2: 10.0.22621.5189
    Fixed versions for 19 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2025-29824
  • CISA's deadline for US federal agencies: 2025-04-29 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each system to the fixed build listed for its Windows version.
  2. Prioritize servers and systems used by many users, since the flaw is exploited in ransomware attacks.
  3. Follow the Microsoft advisory and CISA's required action; discontinue use of products where mitigations are unavailable.
  4. Limit local and interactive logon rights to reduce the number of accounts that could exploit the flaw.
  5. Check systems for signs of compromise, such as unexpected privilege escalation or ransomware activity.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-416 Use After Free

Questions about CVE-2025-29824

Can this be exploited remotely?
Not directly. The attack vector is local and requires a low-privileged account. Attackers typically use such flaws after gaining initial access to raise their privileges to full control.
Is CVE-2025-29824 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-04-08 and notes known ransomware use. US federal agencies had a due date of 2025-04-29.
Which update fixes it?
Each Windows version has its own fixed build in the CVE record, for example 10.0.26100.3775 for Windows 11 Version 24H2 and 10.0.19045.5737 for Windows 10 Version 22H2. Consult the Microsoft advisory for the matching update.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.