| /openbmc/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()
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-defusedxml_0.7.1.bb | 3 parsers that prevent any potentially malicious operation."
|
| /openbmc/linux/drivers/virt/coco/sev-guest/ |
| H A D | Kconfig | 10 the PSP without risk from a malicious hypervisor who wishes to read,
|
| /openbmc/qemu/docs/system/ |
| H A D | security.rst | 27 malicious:
69 could allow malicious guests to gain code execution in QEMU. At this point the
74 malicious guest must not gain control of other guests or access their data.
162 malicious third parties which might try to make unauthorized connections, or
|
| /openbmc/linux/Documentation/admin-guide/hw-vuln/ |
| 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
262 might allow a malicious actor to leak data from the host or from other
|
| H A 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
|
| H A D | reg-file-data-sampling.rst | 7 a malicious actor to infer data values previously used in floating point
|
| H A D | gather_data_sampling.rst | 15 destination vector register instead. This will allow a malicious attacker to
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/vlock/ |
| H A D | vlock_2.2.3.bb | 2 DESCRIPTION = "Sometimes a malicious local user could cause more problems \
|
| /openbmc/linux/Documentation/driver-api/mmc/ |
| H A D | mmc-dev-parts.rst | 40 not accessible through sysfs in order to avoid accidental or malicious
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-xenbus | 40 basis and is known not to be malicious on purpose. Raising
|
| /openbmc/linux/fs/verity/ |
| H A D | Kconfig | 33 protection against malicious disks vs. an ahead-of-time hash.
|
| /openbmc/linux/drivers/firmware/efi/ |
| H A 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
|
| /openbmc/linux/Documentation/security/keys/ |
| H A D | ecryptfs.rst | 37 threats of malicious software, because it is available in clear form only at
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | MirOS | 16 * implied; without malicious intent or gross negligence. In no event
|
| /openbmc/qemu/docs/ |
| H A D | bypass-iommu.txt | 67 devices might send malicious dma request to virtual machine if there is no
|
| /openbmc/linux/Documentation/devicetree/bindings/pci/ |
| H A D | pci.txt | 72 malicious devices to this port.
|
| /openbmc/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
|
| H A D | buslock.rst | 128 malicious or just badly written.
|
| /openbmc/openbmc/meta-security/recipes-scanners/clamav/ |
| H A D | clamav_0.104.4.bb | 2 …an open source antivirus engine for detecting trojans, viruses, malware & other malicious threats."
|
| /openbmc/qemu/qapi/ |
| H A D | dump.json | 58 # of RAM. This can happen for a large guest, or a malicious guest
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | syscall-user-dispatch.rst | 88 malicious application to subvert the mechanism by jumping to an allowed
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A 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
|