Home
last modified time | relevance | path

Searched refs:malicious (Results 1 – 25 of 27) sorted by relevance

12

/Linux-v5.4/Documentation/admin-guide/hw-vuln/
Dl1tf.rst55 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
Dmultihit.rst8 or cache type. A malicious guest running on a virtualized system can
62 Attacks against the iTLB multihit erratum can be mounted from malicious
Dtsx_async_abort.rst61 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
261 might allow a malicious actor to leak data from the host or from other
Dmds.rst53 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
Dspectre.rst128 (BTB) may be shared between hardware threads in a CPU core. A malicious
220 A malicious user process can try to attack another user process,
484 target buffer left by malicious software. Alternatively, the
/Linux-v5.4/Documentation/driver-api/mmc/
Dmmc-dev-parts.rst40 not accessible through sysfs in order to avoid accidental or malicious
/Linux-v5.4/fs/verity/
DKconfig28 protection against malicious disks vs. an ahead-of-time hash.
/Linux-v5.4/Documentation/security/keys/
Decryptfs.rst37 threats of malicious software, because it is available in clear form only at
/Linux-v5.4/Documentation/devicetree/bindings/pci/
Dpci.txt72 malicious devices to this port.
/Linux-v5.4/Documentation/x86/
Dmds.rst109 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
/Linux-v5.4/Documentation/admin-guide/device-mapper/
Ddm-integrity.rst156 Protect sector numbers in the journal from accidental or malicious
158 crc algorithm, to protect against malicious modification, use a
/Linux-v5.4/drivers/net/ethernet/broadcom/bnx2x/
Dbnx2x_sriov.h144 bool malicious; /* true if FW indicated so, until FLR */ member
Dbnx2x_sriov.c905 vf->malicious = false; in bnx2x_vf_flr()
1838 vf->malicious = true; in bnx2x_iov_eq_sp_event()
1920 if (vf->malicious) { in bnx2x_iov_adjust_stats_req()
/Linux-v5.4/Documentation/networking/device_drivers/intel/
Digb.rst164 When a malicious driver attempts to send a spoofed packet, it is dropped by the
Dixgbe.rst491 When a malicious driver attempts to send a spoofed packet, it is dropped by the
Di40e.rst456 When a malicious driver attempts to send a spoofed packet, it is dropped by the
/Linux-v5.4/Documentation/process/
Dmaintainer-pgp-guide.rst696 that their copy of linux.git has not been tampered with by a malicious
836 developer and not to a malicious imposter?
916 importing a malicious key.
961 administrators of the PGP Pathfinder service to not be malicious (in
/Linux-v5.4/Documentation/admin-guide/
Dmodule-signing.rst25 making it harder to load a malicious module into the kernel. The module
/Linux-v5.4/Documentation/filesystems/
Dfsverity.rst42 protection, i.e. detection of accidental (non-malicious) corruption.
46 authentication (detection of malicious modifications) or auditing
64 time it's paged in. This ensures that malicious disk firmware can't
Dfuse.txt210 in all cases except some malicious deadlocks
Dubifs-authentication.rst20 binary to perform a malicious action when executed [DMC-CBC-ATTACK]. Since
Dfscrypt.rst155 Therefore, a malicious user can temporarily associate the wrong key
/Linux-v5.4/Documentation/target/
Dtcmu-design.rst277 Userspace handler process is malicious:
/Linux-v5.4/Documentation/filesystems/configfs/
Dconfigfs.txt73 To avoid a malicious user OOMing the kernel, there's a per-binary attribute
/Linux-v5.4/Documentation/networking/
Dip-sysctl.txt360 a buggy or malicious middlebox or man-in-the-middle can

12