SecOps SignalSecurity Intelligence Workspace
Loading collection status
Vulnerabilities/CVE-2025-24983Public Intelligence Dossier
Source: microsoft · Limited verification•Last verified: •Collection Degraded
CVE-2025-24983ListedHIGH (raw)CVSS 7.0CWE-416

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

Published: 11 Mar 2025•Last updated: 17 Jun 2026, 02:29 PM IST•Source identifier: secure@microsoft.com
Dossier completeness: source-provided sections 3 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Listed
Added11 Mar 2025
Due01 Apr 2025
RansomwareUnknown
CVSS score
7.0HIGH (raw)
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Metric sourcesecure@microsoft.com
EPSS probability
1.4%0.014
Percentile72nd
Weakness type
CWE-416
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

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

SOC priority

Immediate Attention

Actively exploited (source statement)

Yes

Publicly disclosed

Unknown

Risk basis: CISA KEV exploitation signal; Microsoft or Microsoft-managed product relevance; HIGH severity; Known exploitation signal from CISA KEV or ransomware metadata

Affected Products & Remediation

5 source-backed products
Affected products and versions (source)
  • microsoft windows 10 1507 · < 10.0.10240.20947 · NVD CPE · Source
  • microsoft windows 10 1607 · < 10.0.14393.7876 · NVD CPE · Source
  • microsoft windows server 2008 · r2 · NVD CPE · Source
  • microsoft windows server 2012 · r2 · NVD CPE · Source
  • microsoft windows server 2016 · < 10.0.14393.7876 · NVD CPE · Source
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

  • CISA KEV: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Listed
Exploited (source statement)
Yes
Publicly disclosed (source)
Unknown

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched microsoft-enterprise (Affected product: microsoft windows 10 1507, Vendor: microsoft); local-access-review (CVSS AV:L, CVSS PR:L)

Exposure

  1. Identify affected Microsoft products and compare local builds with the MSRC advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · The MSRC product/build mapping establishes applicability. · Rule microsoft-enterprise
  2. Identify hosts reporting this CVE, prioritising shared or multi-user systems.Telemetry: DeviceTvmSoftwareVulnerabilities · A local, low-privilege vector matters most where untrusted users can run code. · Rule local-access-review

Exploitation evidence

  1. Review the advisory's documented behavior on matching hosts before selecting a hunt.Telemetry: DeviceProcessEvents · Product family alone does not justify a CVE-specific detection. · Rule microsoft-enterprise
Show more (2)

Exploitation evidence

  1. Review source-stated impact and relevant application errors on affected hosts; local access alone does not establish privilege escalation.Telemetry: DeviceProcessEvents · The vector establishes local access and low privileges only. Confirm the impact from the advisory before choosing a specific hunt. · Rule local-access-review

Response

  1. Confirm the source-stated KB or mitigation on matching assets.Telemetry: DeviceTvmSoftwareVulnerabilities · A post-update inventory check verifies remediation. · Rule microsoft-enterprise

CISA KEV Record

Catalog entry
11 Mar 2025
Required action due
01 Apr 2025
Known ransomware use
Unknown

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Change History & Source Data

— No recorded material change

CNA / source
secure@microsoft.com
Record status · verification
UPDATED · Microsoft primary source linked; CISA KEV confirmed
CPE
cpe:2.3:o:microsoft:windows_10_1507:*:*:*:*:*:*:x64:*, cpe:2.3:o:microsoft:windows_10_1507:*:*:*:*:*:*:x86:*, cpe:2.3:o:microsoft:windows_10_1607:*:*:*:*:*:*:x64:*, cpe:2.3:o:microsoft:windows_10_1607:*:*:*:*:*:*:x86:*, cpe:2.3:o:microsoft:windows_server_2008:-:sp2:*:*:*:*:x64:*, cpe:2.3:o:microsoft:windows_server_2008:-:sp2:*:*:*:*:x86:*, cpe:2.3:o:microsoft:windows_server_2008:r2:sp1:*:*:*:*:x64:*, cpe:2.3:o:microsoft:windows_server_2012:-:*:*:*:*:*:*:*, cpe:2.3:o:microsoft:windows_server_2012:r2:*:*:*:*:*:*:*, cpe:2.3:o:microsoft:windows_server_2016:*:*:*:*:*:*:*:*

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2025-24983
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2025-24983
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2025-24983"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.
Loading related intelligence

Correlated briefings

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.