# CVE-2025-24983: Microsoft Windows Win32k Use-After-Free

> An authorized local attacker can exploit a use-after-free flaw in the Windows Win32 Kernel Subsystem to elevate privileges.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 11 Mar 2025 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-f4fr-5w7w-pg2w

## What is CVE-2025-24983?

CVE-2025-24983 is a high-severity use after free vulnerability in Microsoft Windows 10 1507, published on 11 Mar 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 Win32 Kernel Subsystem allows an authorized attacker to elevate privileges locally.

Weakness: CWE-416 (Use After Free)

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

It affects 5 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016.

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

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

## Is CVE-2025-24983 being exploited?

Yes. Attackers have exploited CVE-2025-24983 in the wild since at least 11 Mar 2025.

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

What it is: CVE-2025-24983 is a high-severity use after free vulnerability in Microsoft Windows 10 1507, published on 11 Mar 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-24983 in the wild since at least 11 Mar 2025.

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-24983/ (Markdown: https://insights.sbomify.com/CVE-2025-24983/index.md)
```

## Sources

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

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