Patch tracker / CVE reference / CVE-2024-38191
CVE-2024-38191
CVE-2024-38191 is a high severity Microsoft vulnerability with a CVSS score of 7.8. Microsoft has shipped the fix: deploy one of the 12 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.
Risk summary
Not in the CISA KEV catalog. EPSS exploit probability 1.2%. CVSS 7.8 (High).
This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.
This kernel streaming service driver escalation is the low-scored cousin of the Critical kernel streaming bugs from the same period, affecting Windows 10 Version 1809 and Windows Server 2019 at High Severity (CVSS 7.8) with a 1 percent EPSS probability. Different score, same driver, same fix vehicle. Its presence confirms how thoroughly this component was picked over by researchers.
Do this: Verify the month's cumulative update on the 1809 branch, which resolves this along with the rest of the kernel streaming findings.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2024-38191
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Official patch(es) for CVE-2024-38191
Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5040427, KB5040430, KB5040431, KB5040434, KB5040437, KB5040448, KB5040456, KB5040485, KB5040490, KB5040497, KB5040498, KB5040499 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.
Apply the Microsoft security updates below to fix CVE-2024-38191. Each KB page carries the Microsoft Update Catalog download, Microsoft's known issues for the update, a copy-paste PowerShell check for whether it is installed, and the Senserva AI read.
Scope and sources
- Affected products
- Fixed by the same updates
- Authoritative references
Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.