Threats / Microsoft / CVE-2024-38106

CVE-2024-38106 · EUVD no mirror located · GCVE no mirror located Verified 2026-09-19

Microsoft Windows vulnerability

Microsoft Windows Kernel privilege escalation vulnerability exploitable via race condition, allowing local attackers to gain SYSTEM privileges. Actively exploited in the wild.

Verdict

Today item — known-exploited.

A local privilege escalation flaw in Windows Kernel requiring race condition exploitation. Active exploitation in the wild poses significant risk to unpatched systems, particularly those with untrusted local user access or compromised application contexts.

CISA KEV Yes · 2024-08-13⁵EPSS 0.06337 (verify live)⁶CVSS 7³CISA SSVC Exploitation: active · Automatable: no · Impact: total⁴

Is it exploitable?

— the evidence, ranked above the score

Reported exploitation

11 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.

api.msrc.microsoft.com ↗docs.google.com ↗msrc.microsoft.com ↗cisa.gov ↗Confirmed

Exploited in the wild

Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-08-13).

CISA KEV ↗Confirmed

Probability (EPSS)

EPSS 0.06337 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.

FIRST EPSS ↗High

Severity / affected

CVSS 7 (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) · Affected: Microsoft, Windows. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.

CVE.org ↗Reported

Weakness (CWE)

Mapped to CWE-591 CWE-591.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.

CVE.org ↗Reported

CISA SSVC (triage disposition)

Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.

CISA-ADP ↗Reported

Currency of the record

CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.

CISA KEV ↗CVE.org ↗Reported

WeaknessCWE-591 · CWE-591

Who’s exploiting it?

— attribution turns risk into urgency

Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

Why it matters

— the attack path, told twice: adversary, then board

Front door — unauthenticated access narrative 1

Attacker

I execute code with limited local privileges on a target Windows system.

Business

Attacker gains foothold through compromised application, weak credential, or supply chain vector.

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker

I trigger the race condition in the Windows Kernel to escalate my privileges to SYSTEM level.

Business

Attacker obtains highest system privileges, bypassing access controls and security boundaries.

Lateral reach — past segmentation narrative 3

Attacker

I install persistence mechanisms, disable security tools, and move laterally across the network.

Business

Complete system compromise enables data theft, malware deployment, lateral movement, and operational disruption.

What to do

— defensible action

Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.¹

Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.

Coverage & confidence

— what we know, and what we don’t

Established (cited)

KEV listing (CISA)

EPSS probability (FIRST)

11 reported-exploitation source(s)

CVSS 7 — CNA-assigned (CVE.org)

CISA SSVC triage disposition (CVE.org ADP)

CWE weakness mapping — CNA-assigned (CVE.org)

Catalogued by microsoft (CNA)

Named finder/reporter credit (CVE.org)

Coverage gaps — stated, not hidden

No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.

EPSS & exposure are time-varying; verify live at the source.

Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.

Disclosure & credit²

Catalogued by microsoftCNA

Credited with finding itAnonymousfinder

Found an error? Propose a correction.

A correction is a cited counter-claim — it must cite a source, gets reviewed by a second human, and is never auto-applied. See the correction convention and our identity npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.

With JavaScript off: publish a signed kind 1111 Nostr event tagging ["r", "https://basicsecurity.net/threat/cve-2024-38106.html"], ["v", "sha256:359f5820b35facaa50dda6d16125bfa115198eb76090cab5e6c9f42ab36b165c"] (the record version), plus ["src", "<your source URL>"] and ["t", "correction"], per the correction convention. Our identity: npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y. Cite-or-die: an event with no src is a coverage finding, not a proposal.