# CVE-2024-6768: Denial of Service in CLFS.sys

> A low-privilege authenticated user can cause a Blue Screen of Death in Microsoft Windows by triggering a bug check in CLFS.sys.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2024
- **Updated:** 15 Sep 2025
- **Also known as:** GHSA-3wg3-6wwv-v265

## What is CVE-2024-6768?

CVE-2024-6768 is a medium-severity denial of service vulnerability in Microsoft Windows 10, published on 12 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Denial of Service in CLFS.sys in Microsoft Windows 10, Windows 11, Windows Server 2016, Windows Server 2019, and Windows Server 2022 allows a malicious authenticated low-privilege user to cause a Blue Screen of Death via a forced call to the KeBugCheckEx function.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

## Which versions are affected by CVE-2024-6768?


## How do I fix CVE-2024-6768?

No fix has been published for CVE-2024-6768 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-6768 being exploited?

There is no known exploitation of CVE-2024-6768 in the wild and no public exploit code.

Public exploit code:

- https://github.com/fortra/CVE-2024-6768 (github_poc): https://github.com/fortra/CVE-2024-6768

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6768 and fix it if it is affected.

What it is: CVE-2024-6768 is a medium-severity denial of service vulnerability in Microsoft Windows 10, published on 12 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6768 in the wild and no public exploit code.

Affected product: Microsoft Windows 10. 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-2024-6768/ (Markdown: https://insights.sbomify.com/CVE-2024-6768/index.md)
```

## Sources

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

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