Searched refs:malicious (Results 1 – 25 of 46) sorted by relevance
12
| /Linux-v6.6/drivers/net/ethernet/intel/ice/ |
| D | ice_vf_mbx.c | 328 if (is_malvf && !vf_info->malicious) { in ice_mbx_vf_state_handler()
329 vf_info->malicious = 1; in ice_mbx_vf_state_handler()
345 vf_info->malicious = 0; in ice_mbx_clear_malvf()
|
| D | ice_type.h | 797 u8 malicious : 1; member
|
| /Linux-v6.6/drivers/virt/coco/sev-guest/ |
| D | Kconfig | 10 the PSP without risk from a malicious hypervisor who wishes to read,
|
| /Linux-v6.6/Documentation/admin-guide/hw-vuln/ |
| 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
|
| 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
|
| D | mds.rst | 53 incorrect program execution or state changes. But a malicious operation
67 Attacks against the MDS vulnerabilities can be mounted from malicious non-
221 for malicious user space. The exposure can be disabled on the kernel
|
| 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
262 might allow a malicious actor to leak data from the host or from other
|
| D | gather_data_sampling.rst | 15 destination vector register instead. This will allow a malicious attacker to
|
| D | spectre.rst | 128 (BTB) may be shared between hardware threads in a CPU core. A malicious
233 A malicious user process can try to attack another user process,
518 target buffer left by malicious software.
|
| /Linux-v6.6/Documentation/driver-api/mmc/ |
| D | mmc-dev-parts.rst | 40 not accessible through sysfs in order to avoid accidental or malicious
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-devices-xenbus | 40 basis and is known not to be malicious on purpose. Raising
|
| /Linux-v6.6/fs/verity/ |
| D | Kconfig | 33 protection against malicious disks vs. an ahead-of-time hash.
|
| /Linux-v6.6/drivers/firmware/efi/ |
| D | Kconfig | 208 kernel. System firmware may configure the IOMMU to prevent malicious
217 any malicious PCI devices from being able to perform DMA until the
278 This mechanism helps prevent malicious hosts from making changes
|
| /Linux-v6.6/Documentation/security/keys/ |
| D | ecryptfs.rst | 37 threats of malicious software, because it is available in clear form only at
|
| /Linux-v6.6/Documentation/devicetree/bindings/pci/ |
| D | pci.txt | 72 malicious devices to this port.
|
| /Linux-v6.6/Documentation/arch/x86/ |
| D | mds.rst | 109 data cannot be controlled in a way which allows exploitation from malicious
184 flushed either on exit to user space or on VMENTER so malicious code
|
| D | buslock.rst | 128 malicious or just badly written.
|
| /Linux-v6.6/Documentation/admin-guide/ |
| D | syscall-user-dispatch.rst | 88 malicious application to subvert the mechanism by jumping to an allowed
|
| /Linux-v6.6/Documentation/admin-guide/device-mapper/ |
| D | dm-integrity.rst | 161 Protect sector numbers in the journal from accidental or malicious
163 crc algorithm, to protect against malicious modification, use a
|
| /Linux-v6.6/Documentation/userspace-api/ |
| D | iommu.rst | 79 4. A malicious/misbehaving user passing illegal/invalid size but within
|
| /Linux-v6.6/drivers/net/ethernet/broadcom/bnx2x/ |
| D | bnx2x_sriov.h | 145 bool malicious; /* true if FW indicated so, until FLR */ member
|
| /Linux-v6.6/Documentation/networking/device_drivers/ethernet/intel/ |
| D | igb.rst | 164 When a malicious driver attempts to send a spoofed packet, it is dropped by the
|
| 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.
601 malicious traffic from the VF and disable Tx/Rx queues or drop the offending
621 When a malicious driver on a Virtual Function (VF) interface attempts to send a
|
| /Linux-v6.6/Documentation/filesystems/ |
| 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
292 malicious disk, the metadata will indeed match). E.g. to implement
|
| /Linux-v6.6/drivers/infiniband/ulp/rtrs/ |
| D | README | 57 (always_invalidate=N), if he understands and can take the risk of a malicious
|
12
