Kernel compromise via incomplete driver blocklist
Published Sep 8, 2025 · Updated Nov 17, 2025
Incomplete driver blocking in Microsoft Windows allows local users to run vulnerable signed drivers omitted from the endpoint list. The Windows Update-delivered DriverSiPolicy blocklist intentionally omits some rules from Microsoft’s fuller downloadable policy to preserve compatibility. Exposure requires a vulnerable signed driver and an enforcement configuration that relies on the smaller list; Microsoft disputes that this compatibility tradeoff is a vulnerability.
Summary
What happened
Incomplete driver blocking in Microsoft Windows allows local users to run vulnerable signed drivers omitted from the endpoint list. The Windows Update-delivered DriverSiPolicy blocklist intentionally omits some rules from Microsoft’s fuller downloadable policy to preserve compatibility. Exposure requires a vulnerable signed driver and an enforcement configuration that relies on the smaller list; Microsoft disputes that this compatibility tradeoff is a vulnerability.
The record
- CVE
- CVE-2022-50238
- Published
- Sep 8, 2025
- Updated
- Nov 17, 2025
- Vendor
- Microsoft
- Product
- Windows
- Classifications
- CWE-184, CWE-820, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 8, 2025CVE publishedPublication date reported by the CVE source.
- Nov 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10 <=Server 2025
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo