# CVE-2024-30088: Microsoft Windows Kernel TOCTOU Race Condition

> A race condition in the Windows kernel allows attackers to elevate privileges, requiring a patch for all affected Windows versions.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 15 Oct 2024 (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:** 11 Jun 2024
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-h47v-33fm-j33g

## What is CVE-2024-30088?

CVE-2024-30088 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 11 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Windows Kernel Elevation of Privilege Vulnerability

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

It affects 12 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 21h2, Microsoft Windows 11 22h2, Microsoft Windows 11 23h2, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2022 23h2.

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

No fix has been published for CVE-2024-30088 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 5 Nov 2024.

## Is CVE-2024-30088 being exploited?

Yes. Attackers have exploited CVE-2024-30088 in the wild since at least 15 Oct 2024, including in ransomware campaigns.

Public exploit code:

- Kernel exploit for Xbox SystemOS using CVE-2024-30088 (github_poc): https://github.com/exploits-forsale/collateral-damage
- https://github.com/tykawaii98/CVE-2024-30088 (github_poc): https://github.com/tykawaii98/CVE-2024-30088
- 该漏洞存在于 NtQueryInformationToken 函数中，特别是在处理AuthzBasepCopyoutInternalSecurityAttributes 函数时，该漏洞源于内核在操作对象时对锁定机制的不当管理，这一失误可能导致恶意实体意外提升权限。 (github_poc): https://github.com/Zombie-Kaiser/CVE-2024-30088-Windows-poc
- 🆘New Windows Kernel Priviledge Escalation Vulnerability (github_poc): https://github.com/NextGenPentesters/CVE-2024-30088-
- Questa repository contiene una replica (tentativo di replica) scritto in Python per CVE-2024-30088. (github_poc): https://github.com/Admin9961/CVE-2024-30088
- Kernel exploit for Xbox SystemOS using CVE-2024-30088 (github_poc): https://github.com/Justintroup85/exploits-forsale-collateral-damage

## 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-2024-30088 and fix it if it is affected.

What it is: CVE-2024-30088 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 11 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-30088 in the wild since at least 15 Oct 2024, 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-2024-30088/ (Markdown: https://insights.sbomify.com/CVE-2024-30088/index.md)
```

## Sources

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

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