| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | attack_vector_controls.rst | 34 The user-to-kernel attack vector involves a malicious userspace program
54 The user-to-user attack vector involves a malicious userspace program attempting
63 preventing a malicious userspace program from leaking data from another
74 The guest-to-host attack vector involves a malicious VM attempting to leak
88 The guest-to-guest attack vector involves a malicious VM attempting to influence
96 Similar to the user-to-user attack vector, preventing a malicious VM from
107 The cross-thread attack vector involves a malicious userspace program or
108 malicious VM either observing or attempting to influence the behavior of code
|
| H A D | vmscape.rst | 38 Kernel tracks when a CPU has run a potentially malicious guest and issues an
44 from a malicious guest. This is because Spectre-v2 mitigations are applied at
86 run a potentially malicious guest and issues an IBPB before the first
|
| H A D | l1tf.rst | 55 opportunity for side channel attacks to unprivileged malicious code,
72 PTE which is marked non present. This allows a malicious user space
84 malicious user space applications.
89 The fact that L1TF breaks all domain protections allows malicious guest
90 OSes, which can control the PTEs directly, and malicious guest user
98 only to attack data which is present in L1D, a malicious guest running
161 The kernel is unconditionally protected against L1TF attacks from malicious
177 by a potentially malicious guest, it also flushes the guest
518 further, but still allows a malicious guest to explore a limited amount
582 - PTE inversion to protect against malicious user space. This is done
|
| H A D | multihit.rst | 8 or cache type. A malicious guest running on a virtualized system can
62 Attacks against the iTLB multihit erratum can be mounted from malicious
|
| H A D | tsx_async_abort.rst | 61 The victim of a malicious actor does not need to make use of TSX. Only the
77 a result, the malicious actor has to sample as much data as possible and
255 might allow a malicious actor to leak data from the host or from other
|
| H A D | gather_data_sampling.rst | 15 destination vector register instead. This will allow a malicious attacker to
|
| H A D | spectre.rst | 128 (BTB) may be shared between hardware threads in a CPU core. A malicious
232 A malicious user process can try to attack another user process,
538 target buffer left by malicious software.
|
| /linux/drivers/net/ethernet/intel/ice/ |
| H A D | ice_vf_mbx.c | 360 if (is_malvf && !vf_info->malicious) { in ice_mbx_vf_state_handler()
361 vf_info->malicious = 1; in ice_mbx_vf_state_handler()
377 vf_info->malicious = 0; in ice_mbx_clear_malvf()
|
| /linux/Documentation/userspace-api/ |
| H A D | check_exec.rst | 15 security risk of running malicious scripts with respect to the execution
121 The threat is (potential) malicious scripts run by trusted (and not fooled)
139 The threat is malicious scripts run by untrusted users (but trusted code).
|
| /linux/Documentation/driver-api/mmc/ |
| H A D | mmc-dev-parts.rst | 40 not accessible through sysfs in order to avoid accidental or malicious
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-xenbus | 40 basis and is known not to be malicious on purpose. Raising
|
| /linux/fs/verity/ |
| H A D | Kconfig | 27 protection against malicious disks vs. an ahead-of-time hash.
|
| /linux/Documentation/virt/hyperv/ |
| H A D | coco.rst | 73 protect itself against a potentially malicious paravisor just like it
74 protects against a potentially malicious guest.
148 * Interrupt injection. In fully enlightened mode, a malicious hypervisor
174 includes a compromised and potentially malicious host, the guest must guard
196 validate the data before acting on it so that a malicious host cannot induce
203 to protect against a malicious host. See hv_pkt_iter_first().
|
| /linux/Documentation/security/ |
| H A D | snp-tdx-threat-model.rst | 133 malicious, but that there exists a security value in having a small CoCo
216 * - Guest malicious configuration
248 providing a malicious time to the guest or the entropy to the guest
|
| /linux/Documentation/security/keys/ |
| H A D | ecryptfs.rst | 37 threats of malicious software, because it is available in clear form only at
|
| /linux/drivers/firmware/efi/ |
| H A D | Kconfig | 202 kernel. System firmware may configure the IOMMU to prevent malicious
211 any malicious PCI devices from being able to perform DMA until the
281 This mechanism helps prevent malicious hosts from making changes
|
| /linux/Documentation/arch/x86/ |
| H A D | mds.rst | 112 data cannot be controlled in a way which allows exploitation from malicious
200 flushed either on exit to user space or on VMENTER so malicious code
|
| /linux/Documentation/admin-guide/ |
| H A D | syscall-user-dispatch.rst | 93 malicious application to subvert the mechanism by jumping to an allowed
|
| H A D | module-signing.rst | 25 making it harder to load a malicious module into the kernel. The module
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-integrity.rst | 166 Protect sector numbers in the journal from accidental or malicious
168 crc algorithm, to protect against malicious modification, use a
|
| /linux/drivers/net/ethernet/broadcom/bnx2x/ |
| H A D | bnx2x_sriov.h | 145 bool malicious; /* true if FW indicated so, until FLR */ member
|
| /linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | igb.rst | 164 When a malicious driver attempts to send a spoofed packet, it is dropped by the
|
| H A D | ice.rst | 66 support SR-IOV, the virtual function (VF) may be subject to malicious behavior.
73 unexpected, and potentially malicious, frames to be dropped.
645 malicious traffic from the VF and disable Tx/Rx queues or drop the offending
665 When a malicious driver on a Virtual Function (VF) interface attempts to send a
|
| /linux/Documentation/filesystems/ |
| H A D | fsverity.rst | 42 detection of accidental (non-malicious) corruption.
46 authentication (detection of malicious modifications) or auditing
58 time it's paged in. This ensures that malicious disk firmware can't
307 malicious disk, the metadata will indeed match). E.g. to implement
|
| /linux/drivers/infiniband/ulp/rtrs/ |
| H A D | README | 57 (always_invalidate=N), if he understands and can take the risk of a malicious
|