dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 1 Apr 2025.
Windows 10 1507Operating system · Microsoft

CVE-2025-24983

HIGH · 7.0 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 10.0.10240.20947 / 10.0.14393.7876 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Use after free in Windows Win32 Kernel Subsystem allows an authorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Use-after-free vulnerability in the Windows Win32 Kernel Subsystem that allows a locally authenticated attacker to elevate privileges to higher integrity levels.

MitigationApply the Microsoft security update for CVE-2025-24983 through Windows Update or enterprise patch management systems, then verify successful installation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.20947
Windows 10 1607Operating system
Affected:< 10.0.14393.7876
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.7876

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows version and build number
    Run 'winver' from the command line or check 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to see the exact version and build number
    Affected if The build number displayed is lower than 10.0.10240.20947 for Windows 10 1507, or lower than 10.0.14393.7876 for Windows 10 1607 or Windows Server 2016
  2. Determine if the system is Windows Server 2008
    Check if the installed OS is Windows Server 2008 (any edition including R2) using 'systeminfo' or 'winver'
    Affected if The system is any version of Windows Server 2008 or Windows Server 2008 R2 - all versions are affected
  3. Determine if the system is Windows Server 2012
    Check if the installed OS is Windows Server 2012 (any edition including R2) using 'systeminfo' or 'winver'
    Affected if The system is any version of Windows Server 2012 or Windows Server 2012 R2 - all versions are affected
  4. Confirm kernel subsystem is accessible
    Verify the Win32 Kernel Subsystem components are present by confirming the system boots normally and kernel-mode drivers load; this is the default state for any running Windows system
    Affected if The system is running (not in a minimal Safe Mode without kernel drivers) - the vulnerable kernel-mode code is present if the version is affected

You are affected if you are running Windows 10 1507 with build < 10.0.10240.20947, Windows 10 1607 or Windows Server 2016 with build < 10.0.14393.7876, or any version of Windows Server 2008/2012 (including R2 editions).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.20947 / 10.0.14393.7876 or later
Fixed in 10.0.10240.2094710.0.14393.7876
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security update for CVE-2025-24983 through Windows Update or enterprise patch management systems, then verify successful installation.

Recommended fix High confidence

Windows 10 1507: build 10.0.10240.20947+ | Windows 10 1607: build 10.0.14393.7876+ | Windows Server 2016: build 10.0.14393.7876+ | Windows Server 2008/2012: migrate to supported version (no patch available)

  1. Identify the current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. For Windows 10 1507 (Threshold 1): Upgrade to Windows 10 build 10.0.10240.20947 or later via Windows Update or ISO from Microsoft Volume Licensing Service Center
  3. For Windows 10 1607 (Redstone 1): Upgrade to Windows 10 build 10.0.14393.7876 or later via Windows Update or ISO from Microsoft Volume Licensing Service Center
  4. For Windows Server 2016: Upgrade to build 10.0.14393.7876 or later via Windows Server Update Services (WSUS) or Microsoft Update Catalog
  5. For Windows Server 2008/2012 (all versions): These versions are end-of-life; migrate to a supported Windows Server version (2019/2022) as no patches are available
  6. After upgrade, verify the patch is installed by checking for KB5017308 (Windows 10 1607) or subsequent security updates in Windows Update history
Caveat Windows Server 2008/2012 are end-of-life with no security updates; requires OS migration. Ensure application compatibility before upgrading Windows 10 1607 in enterprise environments.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24983 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24983 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data