← Search results
CVE-LINKED INVENTORY33 SECURITY RECORDS
Microsoft Corporation
Win32k
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2023-29336 | 9 May 2023 | Windows 10 Version 1507: 10.0.10240.0 < 10.0.10240.19926; Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.5921; Windows Server 2016: 10.0.14393.0 < 10.0.14393.5921; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.5921; Windows Server 2008 Service Pack 2: 6.0.6003.0 < 6.0.6003.22070; Windows Server 2008 Service Pack 2 (Server Core installation): 6.0.6003.0 < 6.0.6003.22070; Windows Server 2008 Service Pack 2: 6.0.6003.0 < 6.0.6003.22070; Windows Server 2008 R2 Service Pack 1: 6.1.7601.0 < 6.1.7601.26519; Windows Server 2008 R2 Service Pack 1 (Server Core installation): 6.1.7601.0 < 6.1.7601.26519; Windows Server 2012: 6.2.9200.0 < 6.2.9200.24266; Windows Server 2012 (Server Core installation): 6.2.9200.0 < 6.2.9200.24266; Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.20969; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.20969 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-21882 | 11 Jan 2022 | Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.2452, 10.0.0 < 10.0.17763.2452; Windows Server 2019: 10.0.17763.0 < 10.0.17763.2452; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.2452; Windows 10 Version 1909: 10.0.0 < 10.0.18363.2037; Windows 10 Version 21H1: 10.0.0 < 10.0.19043.1466; Windows Server 2022: 10.0.20348.0 < 10.0.20348.469; Windows 10 Version 20H2: 10.0.0 < 10.0.19042.1466; Windows Server version 20H2: 10.0.0 < 10.0.19042.1466; Windows 11 version 21H2: 10.0.0 < 10.0.22000.434; Windows 10 Version 21H2: 10.0.19043.0 < 10.0.19044.1466 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-41357 | 13 Oct 2021 | Windows 10 Version 21H1: 10.0.0 < 10.0.19043.1288; Windows Server 2022: 10.0.0 < 10.0.20348.288; Windows 10 Version 2004: 10.0.0 < 10.0.19041.1288; Windows Server version 2004: 10.0.0 < 10.0.19041.1288; Windows 10 Version 20H2: 10.0.0 < 10.0.19042.1288; Windows Server version 20H2: 10.0.0 < 10.0.19042.1288; Windows 11 version 21H2: 10.0.0 < 10.0.22000.258 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-40450 | 13 Oct 2021 | Windows 10 Version 1809: 10.0.0 < 10.0.17763.2237; Windows Server 2019: 10.0.0 < 10.0.17763.2237; Windows Server 2019 (Server Core installation): 10.0.0 < 10.0.17763.2237; Windows 10 Version 1909: 10.0.0 < 10.0.18363.1854; Windows 10 Version 21H1: 10.0.0 < 10.0.19043.1288; Windows Server 2022: 10.0.0 < 10.0.20348.288; Windows 10 Version 2004: 10.0.0 < 10.0.19041.1288; Windows Server version 2004: 10.0.0 < 10.0.19041.1288; Windows 10 Version 20H2: 10.0.0 < 10.0.19042.1288; Windows Server version 20H2: 10.0.0 < 10.0.19042.1288; Windows 11 version 21H2: 10.0.0 < 10.0.22000.258 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-28310 | 13 Apr 2021 | Windows 10 Version 1803: 10.0.0 < publication; Windows 10 Version 1809: 10.0.0 < publication; Windows Server 2019: 10.0.0 < publication; Windows Server 2019 (Server Core installation): 10.0.0 < publication; Windows 10 Version 1909: 10.0.0 < publication; Windows Server, version 1909 (Server Core installation): 10.0.0 < publication; Windows 10 Version 2004: 10.0.0 < publication; Windows Server version 2004: 10.0.0 < publication; Windows 10 Version 20H2: 10.0.0 < publication; Windows Server version 20H2: 10.0.0 < publication | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-1732 | 25 Feb 2021 | Windows 10 Version 1803: 10.0.0 < publication; Windows 10 Version 1809: 10.0.0 < publication; Windows Server 2019: 10.0.0 < publication; Windows Server 2019 (Server Core installation): 10.0.0 < publication; Windows 10 Version 1909: 10.0.0 < publication; Windows Server, version 1909 (Server Core installation): 10.0.0 < publication; Windows 10 Version 2004: 10.0.0 < publication; Windows Server version 2004: 10.0.0 < publication; Windows 10 Version 20H2: 10.0.0 < publication; Windows Server version 20H2: 10.0.0 < publication | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2020-1054 | 21 May 2020 | Windows 10 Version 1507: 10.0.10240.0 < publication; Windows 10 Version 1607: 10.0.14393.0 < publication; Windows 10 Version 1709: 10.0.0 < publication; Windows 10 Version 1709 for 32-bit Systems: 10.0.0 < publication; Windows 10 Version 1803: 10.0.0 < publication; Windows 10 Version 1809: 10.0.17763.0 < publication, 10.0.0 < publication; Windows 10 Version 1903 for 32-bit Systems: 10.0.0 < publication; Windows 10 Version 1903 for ARM64-based Systems: 10.0.0 < publication; Windows 10 Version 1903 for x64-based Systems: 10.0.0 < publication; Windows 10 Version 1909: 10.0.0 < publication; Windows 7: 6.1.0 < publication; Windows 7 Service Pack 1: 6.1.0 < publication; Windows 8.1: 6.3.0 < publication; Windows Server 2008 R2 Service Pack 1: 6.1.7601.0 < publication; Windows Server 2008 R2 Service Pack 1 (Server Core installation): 6.1.7601.0 < publication; Windows Server 2008 Service Pack 2: 6.0.6003.0 < publication; Windows Server 2008 Service Pack 2 (Server Core installation): 6.0.6003.0 < publication; Windows Server 2012: 6.2.9200.0 < publication; Windows Server 2012 (Server Core installation): 6.2.9200.0 < publication; Windows Server 2012 R2: 6.3.9600.0 < publication; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < publication; Windows Server 2016: 10.0.14393.0 < publication; Windows Server 2016 (Server Core installation): 10.0.14393.0 < publication; Windows Server 2019: 10.0.17763.0 < publication; Windows Server 2019 (Server Core installation): 10.0.17763.0 < publication; Windows Server, version 1803 (Server Core Installation): 10.0.0 < publication; Windows Server, version 1903 (Server Core installation): 10.0.0 < publication; Windows Server, version 1909 (Server Core installation): 10.0.0 < publication | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2019-1458 | 10 Dec 2019 | Windows: 10 for 32-bit Systems, 10 for x64-based Systems, 10 Version 1607 for 32-bit Systems, 10 Version 1607 for x64-based Systems, 7 for 32-bit Systems Service Pack 1, 7 for x64-based Systems Service Pack 1, 8.1 for 32-bit systems, 8.1 for x64-based systems, RT 8.1; Windows Server: 2016, 2016 (Core installation), 2008 for 32-bit Systems Service Pack 2, 2008 for 32-bit Systems Service Pack 2 (Core installation), 2008 for Itanium-Based Systems Service Pack 2, 2008 for x64-based Systems Service Pack 2, 2008 for x64-based Systems Service Pack 2 (Core installation), 2008 R2 for Itanium-Based Systems Service Pack 1, 2008 R2 for x64-based Systems Service Pack 1, 2008 R2 for x64-based Systems Service Pack 1 (Core installation), 2012, 2012 (Core installation), 2012 R2, 2012 R2 (Core installation) | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2019-1132 | 29 Jul 2019 | Windows: 7 for 32-bit Systems Service Pack 1, 7 for x64-based Systems Service Pack 1; Windows Server: 2008 R2 for x64-based Systems Service Pack 1 (Core installation), 2008 R2 for Itanium-Based Systems Service Pack 1, 2008 R2 for x64-based Systems Service Pack 1, 2008 for 32-bit Systems Service Pack 2 (Core installation), 2008 for Itanium-Based Systems Service Pack 2, 2008 for 32-bit Systems Service Pack 2, 2008 for x64-based Systems Service Pack 2, 2008 for x64-based Systems Service Pack 2 (Core installation) | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2019-0859 | 9 Apr 2019 | Windows: 7 for 32-bit Systems Service Pack 1, 7 for x64-based Systems Service Pack 1, 8.1 for 32-bit systems, 8.1 for x64-based systems, RT 8.1, 10 for 32-bit Systems, 10 for x64-based Systems, 10 Version 1607 for 32-bit Systems, 10 Version 1607 for x64-based Systems, 10 Version 1703 for 32-bit Systems, 10 Version 1703 for x64-based Systems, 10 Version 1709 for 32-bit Systems, 10 Version 1709 for x64-based Systems, 10 Version 1803 for 32-bit Systems, 10 Version 1803 for x64-based Systems, 10 Version 1803 for ARM64-based Systems, 10 Version 1809 for 32-bit Systems, 10 Version 1809 for x64-based Systems, 10 Version 1809 for ARM64-based Systems, 10 Version 1709 for ARM64-based Systems; Windows Server: 2008 R2 for x64-based Systems Service Pack 1 (Core installation), 2008 R2 for Itanium-Based Systems Service Pack 1, 2008 R2 for x64-based Systems Service Pack 1, 2008 for 32-bit Systems Service Pack 2 (Core installation), 2012, 2012 (Core installation), 2012 R2, 2012 R2 (Core installation), 2016, 2016 (Core installation), version 1709 (Core Installation), version 1803 (Core Installation), 2019, 2019 (Core installation), 2008 for Itanium-Based Systems Service Pack 2, 2008 for 32-bit Systems Service Pack 2, 2008 for x64-based Systems Service Pack 2, 2008 for x64-based Systems Service Pack 2 (Core installation) | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2019-0803 | 9 Apr 2019 | Windows: 7 for 32-bit Systems Service Pack 1, 7 for x64-based Systems Service Pack 1, 8.1 for 32-bit systems, 8.1 for x64-based systems, RT 8.1, 10 for 32-bit Systems, 10 for x64-based Systems, 10 Version 1607 for 32-bit Systems, 10 Version 1607 for x64-based Systems, 10 Version 1703 for 32-bit Systems, 10 Version 1703 for x64-based Systems, 10 Version 1709 for 32-bit Systems, 10 Version 1709 for x64-based Systems, 10 Version 1803 for 32-bit Systems, 10 Version 1803 for x64-based Systems, 10 Version 1803 for ARM64-based Systems, 10 Version 1809 for 32-bit Systems, 10 Version 1809 for x64-based Systems, 10 Version 1809 for ARM64-based Systems, 10 Version 1709 for ARM64-based Systems; Windows Server: 2008 R2 for x64-based Systems Service Pack 1 (Core installation), 2008 R2 for Itanium-Based Systems Service Pack 1, 2008 R2 for x64-based Systems Service Pack 1, 2008 for 32-bit Systems Service Pack 2 (Core installation), 2012, 2012 (Core installation), 2012 R2, 2012 R2 (Core installation), 2016, 2016 (Core installation), version 1709 (Core Installation), version 1803 (Core Installation), 2019, 2019 (Core installation), 2008 for Itanium-Based Systems Service Pack 2, 2008 for 32-bit Systems Service Pack 2, 2008 for x64-based Systems Service Pack 2, 2008 for x64-based Systems Service Pack 2 (Core installation) | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2019-0797 | 9 Apr 2019 | Windows Server: 2012, 2012 (Core installation), 2012 R2, 2012 R2 (Core installation), 2016, 2016 (Core installation), version 1709 (Core Installation), version 1803 (Core Installation), 2019, 2019 (Core installation); Windows: 8.1 for 32-bit systems, 8.1 for x64-based systems, RT 8.1, 10 for 32-bit Systems, 10 for x64-based Systems, 10 Version 1607 for 32-bit Systems, 10 Version 1607 for x64-based Systems, 10 Version 1703 for 32-bit Systems, 10 Version 1703 for x64-based Systems, 10 Version 1709 for 32-bit Systems, 10 Version 1709 for x64-based Systems, 10 Version 1803 for 32-bit Systems, 10 Version 1803 for x64-based Systems, 10 Version 1803 for ARM64-based Systems, 10 Version 1809 for 32-bit Systems, 10 Version 1809 for x64-based Systems, 10 Version 1809 for ARM64-based Systems, 10 Version 1709 for ARM64-based Systems | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2019-0808 | 9 Apr 2019 | Windows: 7 for 32-bit Systems Service Pack 1, 7 for x64-based Systems Service Pack 1; Windows Server: 2008 R2 for x64-based Systems Service Pack 1 (Core installation), 2008 R2 for Itanium-Based Systems Service Pack 1, 2008 R2 for x64-based Systems Service Pack 1, 2008 for 32-bit Systems Service Pack 2 (Core installation), 2008 for Itanium-Based Systems Service Pack 2, 2008 for 32-bit Systems Service Pack 2, 2008 for x64-based Systems Service Pack 2, 2008 for x64-based Systems Service Pack 2 (Core installation) | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-8589 | 14 Nov 2018 | Windows Server 2008: 32-bit Systems Service Pack 2, 32-bit Systems Service Pack 2 (Server Core installation), Itanium-Based Systems Service Pack 2, x64-based Systems Service Pack 2, x64-based Systems Service Pack 2 (Server Core installation); Windows 7: 32-bit Systems Service Pack 1, x64-based Systems Service Pack 1; Windows Server 2008 R2: Itanium-Based Systems Service Pack 1, x64-based Systems Service Pack 1, x64-based Systems Service Pack 1 (Server Core installation) | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-8453 | 10 Oct 2018 | Windows 7: 32-bit Systems Service Pack 1, x64-based Systems Service Pack 1; Windows Server 2012 R2: (Server Core installation); Windows RT 8.1: Windows RT 8.1; Windows Server 2008: 32-bit Systems Service Pack 2, 32-bit Systems Service Pack 2 (Server Core installation), Itanium-Based Systems Service Pack 2, x64-based Systems Service Pack 2, x64-based Systems Service Pack 2 (Server Core installation); Windows Server 2019: (Server Core installation); Windows Server 2012: (Server Core installation); Windows 8.1: 32-bit systems, x64-based systems; Windows Server 2016: (Server Core installation); Windows Server 2008 R2: Itanium-Based Systems Service Pack 1, x64-based Systems Service Pack 1, x64-based Systems Service Pack 1 (Server Core installation); Windows 10: 32-bit Systems, Version 1607 for 32-bit Systems, Version 1607 for x64-based Systems, Version 1703 for 32-bit Systems, Version 1703 for x64-based Systems, Version 1709 for 32-bit Systems, Version 1709 for x64-based Systems, Version 1803 for 32-bit Systems, Version 1803 for x64-based Systems, Version 1809 for 32-bit Systems, Version 1809 for x64-based Systems, x64-based Systems; Windows 10 Servers: version 1709 (Server Core Installation), version 1803 (Server Core Installation) | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2018-8120 | 9 May 2018 | Windows Server 2008: 32-bit Systems Service Pack 2, 32-bit Systems Service Pack 2 (Server Core installation), Itanium-Based Systems Service Pack 2, x64-based Systems Service Pack 2, x64-based Systems Service Pack 2 (Server Core installation); Windows 7: 32-bit Systems Service Pack 1, x64-based Systems Service Pack 1; Windows Server 2008 R2: Itanium-Based Systems Service Pack 1, x64-based Systems Service Pack 1, x64-based Systems Service Pack 1 (Server Core installation) | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-0263 | 12 May 2017 | Microsoft Windows: Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-0082 | 17 Mar 2017 | The kernel-mode drivers in Microsoft Windows 10 Gold and 1511 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-0081 | 17 Mar 2017 | The kernel-mode drivers in Microsoft Windows 8.1; Windows Server 2012 Gold and R2; Windows RT 8.1; Windows 10 Gold, 1511, and 1607; and Windows Server 2016 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-0080 | 17 Mar 2017 | The kernel-mode drivers in Microsoft Windows 10 Gold, 1511, and 1607 and Windows Server 2016 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-0079 | 17 Mar 2017 | The kernel-mode drivers in Windows 8.1; Windows Server 2012 R2; Windows RT 8.1; and Windows 10 Gold, 1511, and 1607 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-0078 | 17 Mar 2017 | The kernel-mode drivers in Microsoft Windows 8.1; Windows Server 2012 Gold and R2; Windows RT 8.1; Windows 10 Gold, 1511, and 1607; and Windows Server 2016 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-0056 | 17 Mar 2017 | The kernel-mode drivers in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 Gold and R2; Windows RT 8.1; Windows 10 Gold, 1511, and 1607; and Windows Server 2016 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-0026 | 17 Mar 2017 | The kernel-mode drivers in Microsoft Windows 10 Gold, 1511, and 1607 and Windows Server 2016 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2017-0024 | 17 Mar 2017 | The kernel-mode drivers in Microsoft Windows 10 1607 and Windows Server 2016 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2016-7255 | 10 Nov 2016 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2016-0167 | 12 Apr 2016 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2016-0165 | 12 Apr 2016 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2015-2546 | 9 Sep 2015 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2015-2360 | 10 Jun 2015 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2015-1701 | 21 Apr 2015 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2014-4113 | 15 Oct 2014 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2013-3660 | 24 May 2013 | n/a | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.