Lines Matching full:affected

9 are not affected. System environments using virtualization where MMIO access is
61 processors affected by FBSDP, this may expose stale data from the fill buffers
67 into client core fill buffers, processors affected by MFBDS can leak data from
77 Affected Processors
79 Not all the CPUs are affected by all the variants. For instance, most
83 Below is the list of affected Intel processors [#f1]_:
108 If a CPU is in the affected processor list, but not affected by a variant, it
115 Newer processors and microcode update on existing affected processors added new
122 Bit 13 - SBDR_SSDP_NO - When set, processor is not affected by either the
125 Bit 14 - FBSDP_NO - When set, processor is not affected by the Fill Buffer
127 Bit 15 - PSDP_NO - When set, processor is not affected by Primary Stale Data
131 	 enumerate MDS_NO (meaning they are affected by MDS) but that do
153 same mitigation strategy to force the CPU to clear the affected buffers before
157 combination with a microcode update. The microcode clears the affected CPU
164 On MDS affected CPUs, the kernel already invokes CPU buffer clear on
168 For CPUs not affected by MDS or TAA, mitigation is needed only for the attacker
177 Same mitigation as MDS when affected by MDS/TAA, otherwise no mitigation
188 Same mitigation as MDS when processor is also affected by MDS/TAA, otherwise
189 execute VERW at VMENTER only for MMIO capable guests. On CPUs not affected by
208 If the CPU is affected and mmio_stale_data=off is not supplied on the kernel
223      * - 'Not affected'
270 .. [#f1] Affected Processors
271 …/us/en/developer/topic-technology/software-security-guidance/processors-affected-consolidated-prod…