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 6 Jan 2025.
Windows 10 1507Operating system · Microsoft

CVE-2024-35250

HIGH · 7.8 CVSS v3.1 Published 2024-06-11
Fix available
A fix is available. Upgrade to 10.0.10240.20680 / 10.0.14393.7070 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
Windows Kernel-Mode Driver Elevation of Privilege Vulnerability

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

A Windows Kernel-Mode Driver Elevation of Privilege vulnerability exists that allows an authenticated attacker to gain elevated SYSTEM-level privileges on the affected system. This class of vulnerability typically stems from improper input validation, memory corruption, or insufficient access controls within kernel-mode driver code.

MitigationApply the Microsoft security update addressing CVE-2024-35250 as soon as testing permits. Prioritize systems exposed to untrusted users or network paths, and verify driver compatibility post-patch in staging environments.

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.20680
Windows 10 1607Operating system
Affected:< 10.0.14393.7070
Windows 10 1809Operating system
Affected:< 10.0.17763.5936
Windows 10 21h2Operating system
Affected:< 10.0.19044.4529
Windows 10 22h2Operating system
Affected:< 10.0.19045.4529
Windows 11 21h2Operating system
Affected:< 10.0.22000.3019
Windows 11 22h2Operating system
Affected:< 10.0.22621.3737
Windows 11 23h2Operating system
Affected:< 10.0.22631.3737

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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. Check Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the exact Windows build number
    Affected if The displayed version is lower than any of the affected thresholds: 10.0.10240.20680 (1507), 10.0.14393.7070 (1607), 10.0.17763.5936 (1809), 10.0.19044.4529 (21h2), 10.0.19045.4529 (22h2), 10.0.22000.3019 (Win11 21h2), 10.0.22621.3737 (Win11 22h2), or 10.0.22631.3737 (Win11 23h2)
  2. Confirm kernel-mode drivers are present
    Run 'driverquery /v | findstr "Kernel Mode"' or use Device Manager to view kernel-mode driver status
    Affected if Any kernel-mode drivers are loaded on the system, as the vulnerability exists in the kernel-mode driver component
  3. Identify driver file version (if specific driver is known)
    If the vulnerable driver name is known from vendor documentation, right-click the driver file in %SystemRoot%\System32\drivers, select Properties, and check the File version tab
    Affected if The driver file version is lower than the fixed version provided in the Microsoft security update for this CVE

Your system is affected if it runs a Windows version below the fixed build numbers listed and has the vulnerable kernel-mode driver loaded.

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.20680 / 10.0.14393.7070 / 10.0.17763.5936 or later
Fixed in 10.0.10240.2068010.0.14393.707010.0.17763.5936
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security update addressing CVE-2024-35250 as soon as testing permits. Prioritize systems exposed to untrusted users or network paths, and verify driver compatibility post-patch in staging environments.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.20680 | Windows 10 1607: 10.0.14393.7070 | Windows 10 1809: 10.0.17763.5936 | Windows 10 21h2: 10.0.19044.4529 | Windows 10 22h2: 10.0.19045.4529 | Windows 11 21h2: 10.0.22000.3019 | Windows 11 22h2: 10.0.22621.3737 | Windows 11 23h2: 10.0.22631.3737

  1. Identify the current Windows version by running 'winver' or checking System Settings > About
  2. Download and install the June 2024 Windows Security Update (KB5039212 or later) from Microsoft Update Catalog for your specific Windows version
  3. Alternatively, enable Windows Update and check for updates to receive the security patch automatically
  4. After installation, restart the system to complete the patch
  5. Verify the installation by checking the installed updates list or running 'winver' to confirm the version matches or exceeds the fixed version for your Windows release
Caveat Kernel-mode driver updates may cause compatibility issues with third-party drivers; test in staging environment before broad deployment

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
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35250 — 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-2024-35250 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