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

> An authorized local attacker can exploit a use-after-free flaw in the Windows Common Log File System Driver to elevate privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 8 Apr 2025 (CISA KEV), used in ransomware
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Apr 2025
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-74mq-6c57-fxpx

## What is CVE-2025-29824?

CVE-2025-29824 is a high-severity use after free vulnerability in Microsoft Windows 10 1507, published on 8 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2025-29824?

It affects 15 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 22h2, Microsoft Windows 11 23h2, Microsoft Windows 11 24h2, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2022 23h2, Microsoft Windows Server 2025.

## How do I fix CVE-2025-29824?

No fix has been published for CVE-2025-29824 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 29 Apr 2025.

## Is CVE-2025-29824 being exploited?

Yes. Attackers have exploited CVE-2025-29824 in the wild since at least 8 Apr 2025, including in ransomware campaigns.

Public exploit code:

- https://github.com/encrypter15/CVE-2025-29824 (github_poc): https://github.com/encrypter15/CVE-2025-29824
- Use after free in Windows Common Log File System Driver allows an authorized attacker to elevate privileges locally. (github_poc): https://github.com/AfanPan/CVE-2025-29824-Exploit
- note (github_poc): https://github.com/zmkeh/CVE-2025-29824-CLFS-Local-privilege-escalation
- https://github.com/uname1able/CVE-2025-29824 (github_poc): https://github.com/uname1able/CVE-2025-29824

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-29824 and fix it if it is affected.

What it is: CVE-2025-29824 is a high-severity use after free vulnerability in Microsoft Windows 10 1507, published on 8 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-29824 in the wild since at least 8 Apr 2025, including in ransomware campaigns.

Affected product: Microsoft Windows 10 1507. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-29824/ (Markdown: https://insights.sbomify.com/CVE-2025-29824/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-29824
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-29824
- OSV: https://osv.dev/vulnerability/CVE-2025-29824

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-29824/
Summaries are generated and may contain mistakes; the official description above is the record.