Windows Win32 Kernel Subsystem Elevation of Privilege Vulnerability
Summary
Windows Win32 Kernel Subsystem Elevation of Privilege Vulnerability Affected products named by the advisory: Windows Server 2012; Windows Server 2012 (Server Core installation); Windows Server 2012 R2; Windows Server 2012 R2 (Server Core installation); and 6 more. Affected products named by the advisory: Windows Server 2016 (Server Core installation); Windows Server 2019 (Server Core installation); Windows Server 2022, 23H2 Edition (Server Core installation).
What this means
In plain English
Windows Win32 Kernel Subsystem Elevation of Privilege Vulnerability Affected products named by the advisory: Windows Server 2012; Windows Server 2012 (Server Core installation); Windows Server 2012 R2; Windows Server 2012 R2 (Server Core installation); and 6 more. Affected products named by the advisory: Windows Server 2016 (Server Core installation); Windows Server 2019 (Server Core installation); Windows Server 2022, 23H2 Edition (Server Core installation). Privilege escalation can let an existing user or process gain permissions beyond those originally granted.
Vulnerable items
- Windows Server 2012 (Server Core installation) — Windows Server is Microsoft's server operating-system family for identity, application and infrastructure workloads.
- Windows Server 2012 R2 (Server Core installation) — Windows Server is Microsoft's server operating-system family for identity, application and infrastructure workloads.
- Windows Server 2016 (Server Core installation) — Windows Server is Microsoft's server operating-system family for identity, application and infrastructure workloads.
- Windows Server 2019 (Server Core installation) — Windows Server is Microsoft's server operating-system family for identity, application and infrastructure workloads.
- Windows Server 2022, 23H2 Edition (Server Core installation) — Windows Server is Microsoft's server operating-system family for identity, application and infrastructure workloads.
Recommended action
Primary action: update to a vendor-listed fixed release: 10.0.10240.20680, 10.0.14393.7070, 10.0.17763.5936, 10.0.19044.4529, 10.0.19045.4529, 10.0.22000.3019, 10.0.22621.3737, 10.0.22631.3737, 6.2.9200.24919, 6.3.9600.22023, 10.0.20348.2527, 10.0.25398.950.
Rewritten locally from the scraped official advisory data above; no generative API is used. The vendor advisory is authoritative.
- Windows 10 Version 1507 10.0.10240.0 before 10.0.10240.20680
- Windows 10 Version 1607 10.0.14393.0 before 10.0.14393.7070
- Windows 10 Version 1809 10.0.17763.0 before 10.0.17763.5936
- Windows 10 Version 1809 10.0.0 before 10.0.17763.5936
- Windows 10 Version 21H2 10.0.19044.0 before 10.0.19044.4529
- Windows 10 Version 22H2 10.0.19045.0 before 10.0.19045.4529
- Windows 11 version 21H2 10.0.22000.0 before 10.0.22000.3019
- Windows 11 version 22H2 10.0.22621.0 before 10.0.22621.3737
- Windows 11 version 23H2 10.0.22631.0 before 10.0.22631.3737
- Windows 11 Version 23H2 10.0.22631.0 before 10.0.22631.3737
- Windows Server 2012 6.2.9200.0 before 6.2.9200.24919
- Windows Server 2012 (Server Core installation) 6.2.9200.0 before 6.2.9200.24919
Official advisory · high-confidence parse· fetched 14 hours ago·verify at source
- 10.0.10240.20680
- 10.0.14393.7070
- 10.0.17763.5936
- 10.0.19044.4529
- 10.0.19045.4529
- 10.0.22000.3019
- 10.0.22621.3737
- 10.0.22631.3737
- 6.2.9200.24919
- 6.3.9600.22023
- 10.0.20348.2527
- 10.0.25398.950
Official advisory · high-confidence parse· fetched 14 hours ago·verify at source
Mitigation
Upgrade to a fixed release: 10.0.10240.20680, 10.0.14393.7070, 10.0.17763.5936, 10.0.19044.4529, 10.0.19045.4529, 10.0.22000.3019. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 14 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.