Windows CLFS.sys Unrecoverable State / BSoD via ReadFile on Log File Handle (CVE-2026-2636)
by Alisa Belousova · 2026-07-05
- Severity
- Medium
- CVE
- CVE-2026-2636
- Category
- binary
- Affected product
- Windows Common Log File System driver (CLFS.sys, version 10.0.22621.5037 used as reference)
- Affected versions
- Windows 11 23H2 and earlier; Windows 11 2024 LTSC and Windows Server 2025 prior to the September 2025 cumulative update (patched in that update and in Windows 11 25H2)
- Disclosed
- 2026-07-05
- Patch status
- patched
Archive entry
intelseclab/poc-archiveMetadata
| Field | Value |
|---|---|
| Date Added | 2026-07-05 |
| Last Updated | 2026-02 |
| Author / Researcher | Alisa Belousova |
| CVE / Advisory | CVE-2026-2636 |
| Category | binary |
| Severity | Medium |
| CVSS Score | Not specified in source (awaiting official CVSS assignment per repository) |
| Status | PoC |
| Tags | clfs, windows-kernel-driver, bsod, denial-of-service, cwe-159, irp, kebugcheckex, unprivileged |
| Related | N/A |
Affected Target
| Field | Value |
|---|---|
| Software / System | Windows Common Log File System driver (CLFS.sys, version 10.0.22621.5037 used as reference) |
| Versions Affected | Windows 11 23H2 and earlier; Windows 11 2024 LTSC and Windows Server 2025 prior to the September 2025 cumulative update (patched in that update and in Windows 11 25H2) |
| Language / Platform | C++ (Windows user-mode console application calling CLFS Win32 APIs) |
| Authentication Required | Local-only (any unprivileged local user) |
| Network Access Required | No |
Summary
CVE-2026-2636 is a denial-of-service vulnerability in the Windows Common Log File System driver (CLFS.sys). An unprivileged local user can crash the system simply by calling the ReadFile Win32 API on a handle obtained via CreateLogFile — a call sequence CLFS does not expect and does not validate correctly. The author discovered this while researching an unrelated CLFS RCE and found that certain value changes to that PoC instead produced a reliable, non-exploitable BSoD, which they are reporting as its own issue. Unlike many historical CLFS bugs, this does not require a maliciously crafted .blf log file — it is triggered purely through an unexpected but otherwise legitimate sequence of standard Windows API calls (CreateLogFile followed by ReadFile). The included PoC is a minimal Visual C++ console application that performs exactly these two calls to reproduce the crash.
Vulnerability Details
Root Cause
CWE-159 (Improper Handling of Invalid Use of Special Elements): CLFS.sys does not correctly validate the IRP flag combination generated when ReadFile is called on a handle returned by CreateLogFile. Normally at least one of IRP_PAGING_IO or IRP_INPUT_OPERATION is expected to be set; when both are unset (as happens with this specific overlapped ReadFile call pattern), the driver follows an incorrect handling path that leads to an unrecoverable inconsistency and a call to KeBugCheckEx.
Attack Vector
- Unprivileged local user runs a program that deletes any pre-existing
MyLogFile.blfand callsCreateLogFileto create/open a new CLFS log (LOG:MyLogFile) withFILE_FLAG_OVERLAPPED. - The program calls
ReadFileon the returned handle with anOVERLAPPEDstructure — a call sequence CLFS.sys does not correctly validate. - The resulting IRP has neither
IRP_PAGING_IOnorIRP_INPUT_OPERATIONset, driving CLFS.sys into an invalid internal state. - CLFS.sys detects the unrecoverable inconsistency and calls
KeBugCheckEx, crashing the entire system (BSoD) — no crafted log file content or elevated privileges are required.
Impact
Reliable, unprivileged local denial-of-service: any standard user can crash the entire Windows system, causing an outage/reboot.
Environment / Lab Setup
Target: Windows 11 23H2 or earlier / Windows 11 2024 LTSC / Windows Server 2025, prior to September 2025 cumulative update
Attacker: Visual Studio (C++ toolchain), local unprivileged user account on the target machine
Proof of Concept
PoC Script
See
ConsoleApplication12/CVE-2026-2636_PoC.cppand the accompanying Visual Studio project files (ConsoleApplication12.sln,ConsoleApplication12.vcxproj) in this folder.
| |
The program deletes any existing MyLogFile.blf, opens a new CLFS log via CreateLogFile, then calls ReadFile on the handle with an overlapped structure — this unexpected but legitimate API sequence drives CLFS.sys into an unrecoverable state and triggers an immediate BSoD.
Detection & Indicators of Compromise
Signs of compromise:
- System crash (BSoD) with a bug check pointing into
CLFS.sysshortly after execution of an unfamiliar user-mode process - Presence of an unexpected
.blflog file (e.g.MyLogFile.blf) created by a standard user account - Crash dump analysis showing a
ReadFilecall on a CLFS log handle in the failing call stack
Remediation
| Action | Detail |
|---|---|
| Primary fix | Apply the September 2025 cumulative update for Windows 11 2024 LTSC / Windows Server 2025, or upgrade to Windows 11 25H2, which shipped patched |
| Interim mitigation | Restrict local logon to untrusted users where possible; monitor for unexpected CLFS log file creation/read patterns from standard user processes until patched |
References
Notes
Mirrored from https://github.com/oxfemale/CVE-2026-2636_PoC on 2026-07-05.