dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2024-38191

HIGH · 7.8 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 10.0.14393.7159 / 10.0.17763.6054 or later.
See remediation →
80/100
Remediation priority · High
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
Kernel Streaming Service 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
How this class of weakness works · CWE-362

Two operations that should be atomic can interleave, so an attacker who wins a narrow timing window reaches an inconsistent, exploitable state. These bugs are subtle and easy to miss in review. Fixing them properly means correct locking or atomic operations around the shared resource.

General guidance for the race condition class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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 1607Operating system
Affected:< 10.0.14393.7159
Windows 10 1809Operating system
Affected:< 10.0.17763.6054
Windows 10 21h2Operating system
Affected:< 10.0.19044.4651
Windows 10 22h2Operating system
Affected:< 10.0.19045.4651
Windows 11 21h2Operating system
Affected:< 10.0.22000.3079
Windows 11 22h2Operating system
Affected:< 10.0.22621.3880
Windows 11 23h2Operating system
Affected:< 10.0.22631.3880
Windows Server 2008Operating system
Affected:all versions= r2

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

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.14393.7159 / 10.0.17763.6054 / 10.0.19044.4651 or later
Fixed in 10.0.14393.715910.0.17763.605410.0.19044.4651
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Windows 10 1607: 10.0.14393.7159 or later | Windows 10 1809: 10.0.17763.6054 or later | Windows 10 21h2: 10.0.19044.4651 or later | Windows 10 22h2: 10.0.19045.4651 or later | Windows 11 21h2: 10.0.22000.3079 or later | Windows 11 22h2: 10.0.22621.3880 or later | Windows 11 23h2: 10.0.22631.3880 or

  1. Open Settings on the Windows system
  2. Navigate to Windows Update (or run 'ms-settings:windowsupdate')
  3. Click 'Check for updates' and install all available security updates
  4. For Windows Server systems, use Server Manager or WSUS to deploy the latest security updates
  5. Reboot the system after installing updates
  6. Verify the installed KB by checking Windows Update history - the fix is included in the July 2024 security updates (KB5002427 for Windows 10 1607, KB5001402 for Windows 10 1809, KB5003171 for Windows 10 21h2/22h2, KB5001402 for Windows 11 21h2/22h2, and KB5003171 for Windows 11 23h2)
Caveat Standard Windows security update - no breaking changes expected for this privilege escalation patch; Windows Server 2008 R2 requires Extended Security Updates (ESU) program enrollment

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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