|
10 | 10 | ms.custom: include file
|
11 | 11 | ---
|
12 | 12 |
|
13 |
| -This article provides guidance for a new class of silicon based micro-architectural and speculative execution side-channel vulnerabilities that affect many modern processors and operating systems. This includes Intel, AMD, and ARM. Specific details for these silicon-based vulnerabilities can be found in the following security advisories: |
| 13 | +This article provides guidance for a new class of silicon based micro-architectural and speculative execution side-channel vulnerabilities that affect many modern processors and operating systems. This includes Intel, AMD, and ARM. Specific details for these silicon-based vulnerabilities can be found in the following security advisories and CVEs: |
14 | 14 | - [ADV180002 - Guidance to mitigate speculative execution side-channel vulnerabilities](https://msrc.microsoft.com/update-guide/vulnerability/ADV180002)
|
15 | 15 | - [ADV180012 - Microsoft Guidance for Speculative Store Bypass](https://msrc.microsoft.com/update-guide/vulnerability/ADV180012)
|
16 | 16 | - [ADV180013 - Microsoft Guidance for Rogue System Register Read](https://msrc.microsoft.com/update-guide/vulnerability/ADV180013)
|
17 | 17 | - [ADV180016 - Microsoft Guidance for Lazy FP State Restore](https://msrc.microsoft.com/update-guide/vulnerability/ADV180016)
|
18 | 18 | - [ADV180018 - Microsoft Guidance to mitigate L1TF variant](https://msrc.microsoft.com/update-guide/vulnerability/ADV180018)
|
19 | 19 | - [ADV190013 - Microsoft Guidance to mitigate Microarchitectural Data Sampling vulnerabilities](https://msrc.microsoft.com/update-guide/vulnerability/ADV190013)
|
20 | 20 | - [ADV220002 - Microsoft Guidance on Intel Processor MMIO Stale Data Vulnerabilities](https://msrc.microsoft.com/update-guide/vulnerability/ADV220002)
|
| 21 | +- [CVE-2022-23816](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-23816) |
| 22 | +- [CVE-2022-21123](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-23825) |
21 | 23 |
|
22 | 24 |
|
23 | 25 | The disclosure of these CPU vulnerabilities has resulted in questions from customers seeking more clarity.
|
@@ -106,6 +108,11 @@ CPU Get NumberOfCores,NumberOfLogicalProcessors /Format:List
|
106 | 108 |
|
107 | 109 | If the number of logical processors is greater than physical processors (cores), then hyper-threading is enabled. If you are running a hyper-threaded VM, [contact Azure Support](https://aka.ms/MicrocodeEnablementRequest-SupportTechnical) to get hyper-threading disabled. Once hyper-threading is disabled, support will require a full VM reboot. Refer to [Core count](#core-count) to understand why your VM core count decreased.
|
108 | 110 |
|
| 111 | +### Option 3 |
| 112 | + |
| 113 | +For [CVE-2022-23816](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-23816) and [CVE-2022-21123](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-23825) (AMD CPU Branch Type Confusion), follow both **Option 1** and **Option 2** above. |
| 114 | + |
| 115 | + |
109 | 116 |
|
110 | 117 | ### Linux
|
111 | 118 |
|
@@ -151,4 +158,4 @@ When a hyper-threaded VM is created, Azure allocates 2 threads per core - these
|
151 | 158 |
|
152 | 159 | ## Next steps
|
153 | 160 |
|
154 |
| -For more information about how security is integrated into every aspect of Azure, see [Azure Security Documentation](../articles/security/index.yml). |
| 161 | +For more information about how security is integrated into every aspect of Azure, see [Azure Security Documentation](../articles/security/index.yml). |
0 commit comments