| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | indirect-target-selection.rst | 28 Below is the list of ITS affected CPUs [#f2]_ [#f3]_:
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
44 ROCKETLAKE 06_A7H Not affected Affected
47 - All affected CPUs enumerate Enhanced IBRS feature.
48 - IBPB isolation is affected on all ITS affected CPUs, and need a microcode
50 - None of the affected CPUs enumerate BHI_CTRL which was introduced in Golden
[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
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
[all …]
|
| H A D | vmscape.rst | 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 | tsx_async_abort.rst | 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
152 off This option disables the TAA mitigation on affected platforms.
154 is affected, the system is vulnerable.
156 full TAA mitigation is enabled. If TSX is enabled, on an affected
158 systems which are MDS-affected and deploy MDS mitigation,
[all …]
|
| H A D | special-register-buffer-data-sampling.rst | 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 | 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 | cross-thread-rsb.rst | 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 | spectre.rst | 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
|
| H A D | multihit.rst | 79 * - Not affected
141 auto Enable mitigation only if the platform is affected and the kernel
|
| /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/m68k/fpsp040/ |
| H A D | x_ovfl.S | 16 | destination is not affected. For 68881 compatibility, the
174 | CCs are defined to be 'not affected' for the opclass3 instruction.
|
| /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
|
| H A D | security-bugs.rst | 54 the reporter or an affected party for up to 7 calendar days from the start
94 mailing list UNTIL a fix is accepted by the affected code's maintainers
|
| /linux/Documentation/hwmon/ |
| H A D | aspeed-g6-pwm-tach.rst | 25 affected by fan signal glitch.
|
| /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/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-light-isl29018 | 16 is less affected by the ambient IR noise variation.
|
| H A D | sysfs-devices-state_synced | 21 at the time the kernel starts are not affected or limited in
|
| /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/sound/soc/sdca/ |
| H A D | sdca_asoc.c | 431 struct sdca_ge_control *affected = &mode->controls[j]; in entity_parse_pde()
434 if (affected->id != entity->id || in entity_parse_pde()
435 affected->sel != SDCA_CTL_SU_SELECTOR || in entity_parse_pde()
436 !affected->val) in entity_parse_pde()
439 if (affected->val - 1 >= entity->num_sources) { in entity_parse_pde()
441 entity->label, affected->val); in entity_parse_pde()
459 entity->sources[affected->val - 1]->label); in entity_parse_su_device()
475 struct sdca_ge_control *affected = &mode->controls[j]; entity_parse_su_device() local
|
| /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.
595 the kernel if an affected CPU is detected.
615 the kernel if an affected CPU is detected.
643 When running a compat (AArch32) userspace on an affected Cortex-A53
652 the kernel if an affected CPU is detected.
676 of hardware DBM locally on the affected cores. CPUs not affected by
[all …]
|
| /linux/drivers/parisc/ |
| H A D | README.dino | 11 ** not affected."
|
| /linux/arch/m68k/ |
| H A D | Kconfig.debug | 17 PROM console functionality on Sun 3x is not affected by this option.
|
| /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
|
| /linux/Documentation/admin-guide/pm/ |
| H A D | cpufreq_drivers.rst | 103 1.2 Platforms affected
180 1.2 Platforms affected:
218 /sys filesystem and how their values are affected by the PCC driver:
|