| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | indirect-target-selection.rst | 26 Affected CPUs
28 Below is the list of ITS affected CPUs [#f2]_ [#f3]_:
34 SKYLAKE_X (step >= 6) 06_55H Affected Affected
35 ICELAKE_X 06_6AH Not affected Affected
36 ICELAKE_D 06_6CH Not affected Affected
37 ICELAKE_L 06_7EH Not affected Affected
38 TIGERLAKE_L 06_8CH Not affected Affected
39 TIGERLAKE 06_8DH Not affected Affected
40 KABYLAKE_L (step >= 12) 06_8EH Affected Affected
41 KABYLAKE (step >= 13) 06_9EH Affected Affected
[all …]
|
| H A D | processor_mmio_stale_data.rst | 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
[all …]
|
| H A D | tsx_async_abort.rst | 10 Affected processors
19 Whether a processor is affected or not can be read out from the TAA
99 …- The CPU is affected by this vulnerability and the microcode and kernel mitigation are not applie…
118 * - 'Not affected'
119 - The CPU is not affected by this issue.
124 The kernel detects the affected CPUs and the presence of the microcode which is
125 required. If a CPU is affected and the microcode is available, then the kernel
135 Affected systems where the host has TAA microcode and TAA is mitigated by
152 off This option disables the TAA mitigation on affected platforms.
154 is affected, the system is vulnerable.
[all …]
|
| H A D | vmscape.rst | 13 Affected processors
16 The following CPU families are affected by VMSCAPE:
20 - Cascade Lake generation - (Parts affected by ITS guest/host separation)
21 - Alder Lake and newer (Parts affected by BHI)
23 Note that, BHI affected parts that use BHB clearing software mitigation e.g.
75 * 'Not affected':
110 not known to be affected.
|
| H A D | special-register-buffer-data-sampling.rst | 17 Affected processors
20 be affected.
22 A processor is affected by SRBDS if its Family_Model and stepping is
25 latter class of processors are only affected when Intel TSX is enabled
26 by software using TSX_CTRL_MSR otherwise they are not affected.
118 affected platforms.
130 Not affected Processor not vulnerable
141 affected but with no way to know if host
|
| H A D | cross-thread-rsb.rst | 18 Affected processors
38 Affected SMT-capable processors support 1T and 2T modes of execution when SMT
46 In affected processors, the return address predictor (RAP) is partitioned
61 An attack can be mounted on affected processors by performing a series of CALL
|
| H A D | gather_data_sampling.rst | 76 use the microcode mitigation when available or disable AVX on affected systems
89 Not affected Processor not vulnerable.
102 affected but with no way to know if host
|
| H A D | spectre.rst | 13 Affected processors
36 Whether a processor is affected or not can be read out from the Spectre
341 * - 'Not affected'
380 'Not affected' The processor is not vulnerable
427 'PBRSB-eIBRS: SW sequence' CPU is affected and protection of RSB on VMEXIT enabled
429 'PBRSB-eIBRS: Not affected' CPU is not affected by PBRSB
436 * - BHI: Not affected
437 - System is not affected
|
| /linux/Documentation/arch/x86/ |
| H A D | mds.rst | 74 thread case (SMT off): Force the CPU to clear the affected buffers.
78 the affected CPU buffers when the VERW instruction is executed.
83 VERW can be avoided. If the CPU is not affected by L1TF then VERW needs to
119 off Mitigation is disabled. Either the CPU is not affected or
122 full Mitigation is enabled. CPU is affected and MD_CLEAR is
125 vmwerv Mitigation is enabled. CPU is affected and MD_CLEAR is not
132 If the CPU is affected and mds=off is not supplied on the kernel command
143 on affected CPUs when the mitigation is not disabled on the kernel
174 cleared on affected CPUs when SMT is active. This addresses the
181 The idle clearing is enabled on CPUs which are only affected by MSBDS
[all …]
|
| H A D | tsx_async_abort.rst | 37 off Mitigation is disabled. Either the CPU is not affected or
43 verw Mitigation is enabled. CPU is affected and MD_CLEAR is
46 ucode needed Mitigation is enabled. CPU is affected and MD_CLEAR is not
53 If the CPU is affected and the "tsx_async_abort" kernel command line parameter is
|
| /linux/arch/x86/kernel/ |
| H A D | smp.c | 69 * 5AP. symmetric IO mode (normal Linux operation) not affected.
71 * 6AP. 'noapic' mode might be affected - fixed in later steppings
94 * 6AP. not affected - worked around in hardware
95 * 7AP. not affected - worked around in hardware
97 * 9AP. only 'noapic' mode affected. Might generate spurious
100 * 10AP. not affected - worked around in hardware
104 * 12AP. not affected - worked around in hardware
105 * 13AP. not affected - worked around in hardware
107 * 15AP. not affected - worked around in hardware
108 * 16AP. not affected - worked around in hardware
[all …]
|
| /linux/arch/arm64/ |
| H A D | Kconfig | 460 The affected design reports FEAT_HAFDBS as not implemented in
510 the kernel if an affected CPU is detected.
532 the kernel if an affected CPU is detected.
555 only patch the kernel if an affected CPU is detected.
577 the kernel if an affected CPU is detected.
588 Affected Cortex-A57 parts might deadlock when exclusive load/store
595 the kernel if an affected CPU is detected.
606 Affected Cortex-A57 parts might report a Stage 2 translation
615 the kernel if an affected CPU is detected.
627 Affected parts may corrupt the AES state if an interrupt is
[all …]
|
| /linux/security/integrity/evm/ |
| H A D | evm_main.c | 435 * @dentry: pointer to the affected dentry
452 * @dentry: pointer to the affected dentry
575 * @dentry: pointer to the affected dentry
576 * @xattr_name: pointer to the affected extended attribute name
613 * @dentry: pointer to the affected dentry
614 * @xattr_name: pointer to the affected extended attribute name
663 * @dentry: pointer to the affected dentry
716 * @dentry: pointer to the affected dentry
767 * @xattr_name: pointer to the affected extended attribute name
792 * @dentry: pointer to the affected dentry
[all …]
|
| /linux/arch/alpha/kernel/ |
| H A D | bugs.c | 26 return sprintf(buf, "Not affected\n"); in cpu_show_meltdown()
35 return sprintf(buf, "Not affected\n"); in cpu_show_spectre_v1()
44 return sprintf(buf, "Not affected\n"); in cpu_show_spectre_v2()
|
| /linux/tools/arch/x86/include/asm/ |
| H A D | cpufeatures.h | 475 #define X86_FEATURE_SRSO_NO (20*32+29) /* CPU is not affected by SRSO */
476 #define X86_FEATURE_SRSO_USER_KERNEL_NO (20*32+30) /* CPU is not affected by SRSO across user/kerne…
530 #define X86_BUG_AMD_E400 X86_BUG(13) /* "amd_e400" CPU is among the affected by Erratum 400 */
531 #define X86_BUG_CPU_MELTDOWN X86_BUG(14) /* "cpu_meltdown" CPU is affected by meltdown attack and …
532 #define X86_BUG_SPECTRE_V1 X86_BUG(15) /* "spectre_v1" CPU is affected by Spectre variant 1 attack…
533 #define X86_BUG_SPECTRE_V2 X86_BUG(16) /* "spectre_v2" CPU is affected by Spectre variant 2 attack…
534 #define X86_BUG_SPEC_STORE_BYPASS X86_BUG(17) /* "spec_store_bypass" CPU is affected by speculative…
535 #define X86_BUG_L1TF X86_BUG(18) /* "l1tf" CPU is affected by L1 Terminal Fault */
536 #define X86_BUG_MDS X86_BUG(19) /* "mds" CPU is affected by Microarchitectural data sampling */
537 #define X86_BUG_MSBDS_ONLY X86_BUG(20) /* "msbds_only" CPU is only affected by the MSDBS variant …
[all …]
|
| /linux/arch/x86/include/asm/ |
| H A D | cpufeatures.h | 477 #define X86_FEATURE_SRSO_NO (20*32+29) /* CPU is not affected by SRSO */
478 #define X86_FEATURE_SRSO_USER_KERNEL_NO (20*32+30) /* CPU is not affected by SRSO across user/kerne…
541 #define X86_BUG_AMD_E400 X86_BUG(13) /* "amd_e400" CPU is among the affected by Erratum 400 */
542 #define X86_BUG_CPU_MELTDOWN X86_BUG(14) /* "cpu_meltdown" CPU is affected by meltdown attack and …
543 #define X86_BUG_SPECTRE_V1 X86_BUG(15) /* "spectre_v1" CPU is affected by Spectre variant 1 attack…
544 #define X86_BUG_SPECTRE_V2 X86_BUG(16) /* "spectre_v2" CPU is affected by Spectre variant 2 attack…
545 #define X86_BUG_SPEC_STORE_BYPASS X86_BUG(17) /* "spec_store_bypass" CPU is affected by speculative…
546 #define X86_BUG_L1TF X86_BUG(18) /* "l1tf" CPU is affected by L1 Terminal Fault */
547 #define X86_BUG_MDS X86_BUG(19) /* "mds" CPU is affected by Microarchitectural data sampling */
548 #define X86_BUG_MSBDS_ONLY X86_BUG(20) /* "msbds_only" CPU is only affected by the MSDBS variant …
[all …]
|
| /linux/Documentation/process/ |
| H A D | embargoed-hardware-issues.rst | 46 While hardware security issues are often handled by the affected silicon
129 description of the problem and a list of any known affected silicon. If
130 your organization builds or distributes the affected hardware, we encourage
131 you to also consider what other hardware could be affected. The disclosing
132 party is responsible for contacting the affected silicon vendors in a
229 To allow the affected silicon vendors to work with their internal teams and
233 Designated representatives of the affected silicon vendors are
236 response team about the handover. The affected silicon vendor must
|
| /linux/include/linux/ |
| H A D | cpu_pm.h | 28 * CPU notifications apply to a single CPU and must be called on the affected
29 * CPU. They are used to save per-cpu context for affected blocks.
32 * are used to save any global context for affected blocks, and must be called
|
| /linux/drivers/net/can/rockchip/ |
| H A D | rockchip_canfd-rx.c | 140 * Not affected if: in rkcanfd_rxstx_filter()
148 /* Not affected if: in rkcanfd_rxstx_filter()
156 /* Not affected if: in rkcanfd_rxstx_filter()
162 /* Not affected if: in rkcanfd_rxstx_filter()
169 /* Affected by Erratum 6 */ in rkcanfd_rxstx_filter()
|
| /linux/arch/riscv/kernel/ |
| H A D | bugs.c | 49 return sprintf(buf, "Not affected\n"); in cpu_show_ghostwrite()
58 return sprintf(buf, "Not affected\n"); in cpu_show_ghostwrite()
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | actions,s500-pinctrl.yaml | 73 List of gpio pin groups affected by the functions specified in
123 List of gpio pin groups affected by the drive-strength property
141 List of gpio pins affected by the bias-pull-* and
|
| /linux/Documentation/devicetree/bindings/reset/ |
| H A D | reset.txt | 23 the DT node of each affected HW block, since if activated, an unrelated block
26 children of the bus are affected by the reset signal, or an individual HW
|
| /linux/Documentation/filesystems/ |
| H A D | quota.rst | 83 - major number of a device with the affected filesystem
85 - minor number of a device with the affected filesystem
|
| /linux/arch/mips/include/asm/ |
| H A D | sync.h | 16 * 2) Ordering barriers, which only ensure that affected memory operations
135 * at each affected branch target.
156 * optimized memory barrier primitives."). Here we specify that the affected
|
| /linux/Documentation/admin-guide/ |
| H A D | reporting-regressions.rst | 144 Developers of the affected code area should try to locate the culprit on their
162 affected users to narrow down the search range together.
221 affected users with a solution in a timely manner and prevent more users from
257 affected area and often Linus Torvalds himself try very hard to fix security
268 developers of the affected code area should look into the issue to find a fix
294 Does the "no regression" rule apply if I seem to be the only affected person?
302 to be affected by a regression, it for the greater good might be in their and
|