Home
last modified time | relevance | path

Searched refs:attack (Results 1 – 25 of 54) sorted by relevance

123

/Linux-v6.6/Documentation/admin-guide/hw-vuln/
Dspectre.rst69 The bounds check bypass attack :ref:`[2] <spec_ref2>` takes advantage
92 The branch target injection attack takes advantage of speculative
116 the attack revealing useful data.
118 One other variant 2 attack vector is for the attacker to poison the
123 return instructions. This attack can be mitigated by flushing the return
134 Yet another variant 2 attack vector is for the attacker to poison the
141 Currently the only known real-world BHB attack vector is via
150 The following list of attack scenarios have been anticipated, but may
151 not cover all possible attack vectors.
162 a pointer for a Spectre variant 1 attack. The index or pointer
[all …]
Dl1tf.rst56 similar to the Meltdown attack.
59 allows to attack any physical memory address in the system and the attack
60 works across all protection domains. It allows an attack of SGX and also
73 application to attack the physical memory to which these PTEs resolve.
78 The Linux kernel contains a mitigation for this attack vector, PTE
92 PTE inversion mitigation for L1TF, to attack physical host memory.
98 only to attack data which is present in L1D, a malicious guest running
99 on one Hyperthread can attack the data which is brought into the L1D by
103 If the processor does not support Extended Page Tables, the attack is
107 While solutions exist to mitigate these attack vectors fully, these
[all …]
Dsrso.rst58 does address User->User and VM->VM attack vectors.
114 attack vectors, including the local User->Kernel one.
120 new attack vectors appear.
Dgather_data_sampling.rst17 attacks. GDS is a purely sampling-based attack.
44 attack, and re-enable it.
Dmds.rst55 allows in turn to infer the value via a cache side channel attack.
74 the TLBleed attack samples can be postprocessed successfully.
220 to use MWAIT in user space (Ring 3) which opens an potential attack vector
Dcross-thread-rsb.rst61 An attack can be mounted on affected processors by performing a series of CALL
Dcore-scheduling.rst16 A cross-HT attack involves the attacker and victim running on different Hyper
135 HT1 (attack) HT2 (victim)
/Linux-v6.6/Documentation/security/
Dself-protection.rst9 and actively detecting attack attempts. Not all topics are explored in
20 attack surface. (Especially when they have the ability to load arbitrary
114 bug to an attack.
127 unexpectedly extend the available attack surface. (The on-demand loading
146 to gain execution control during an attack, By far the most commonly
149 kind of attack exist, and protections exist to defend against them.
164 A less well understood attack is using a bug that triggers the
166 allocations. With this attack it is possible to write beyond the end of
200 defense, in that an attack must gather enough information about a
224 mounting a successful attack, making the location non-deterministic
Dlandlock.rst17 expose a minimal attack surface.
86 deputy attack).
/Linux-v6.6/include/uapi/sound/
Dasound_fm.h39 unsigned char attack; /* 4 bits: attack rate */ member
/Linux-v6.6/Documentation/input/devices/
Diforce-protocol.rst126 0a-0b Address of attack and fade parameters, or ffff if none.
147 02-03 Duration of attack (little endian encoding, in ms)
148 04 Level at end of attack. Signed byte.
356 - attack and fade : 0e
/Linux-v6.6/sound/pci/asihpi/
Dhpi.h1382 u16 hpi_meter_set_peak_ballistics(u32 h_control, u16 attack, u16 decay);
1384 u16 hpi_meter_set_rms_ballistics(u32 h_control, u16 attack, u16 decay);
1386 u16 hpi_meter_get_peak_ballistics(u32 h_control, u16 *attack, u16 *decay);
1388 u16 hpi_meter_get_rms_ballistics(u32 h_control, u16 *attack, u16 *decay);
1618 u32 attack);
Dhpifunc.c1886 u32 attack) in hpi_compander_set_attack_time_constant() argument
1888 return hpi_control_param_set(h_control, HPI_COMPANDER_ATTACK, attack, in hpi_compander_set_attack_time_constant()
1893 u32 *attack) in hpi_compander_get_attack_time_constant() argument
1896 index, attack, NULL); in hpi_compander_get_attack_time_constant()
2062 u16 hpi_meter_set_rms_ballistics(u32 h_control, u16 attack, u16 decay) in hpi_meter_set_rms_ballistics() argument
2065 attack, decay); in hpi_meter_set_rms_ballistics()
2070 u32 attack; in hpi_meter_get_rms_ballistics() local
2075 &attack, &decay); in hpi_meter_get_rms_ballistics()
2078 *pn_attack = (unsigned short)attack; in hpi_meter_get_rms_ballistics()
2085 u16 hpi_meter_set_peak_ballistics(u32 h_control, u16 attack, u16 decay) in hpi_meter_set_peak_ballistics() argument
[all …]
/Linux-v6.6/Documentation/devicetree/bindings/sound/
Dcs35l36.txt113 - cirrus,cirrus,vpbr-atk-rate : Attenuation attack step rate. Configures the
132 - cirrus,vpbr-mute-en : During the attack state, if the vpbr-max-attn value
/Linux-v6.6/Documentation/userspace-api/
Dno_new_privs.rst52 - By itself, ``no_new_privs`` can be used to reduce the attack surface
/Linux-v6.6/net/ipv4/
DKconfig99 attack or a misconfigured system somewhere. The information is
271 Normal TCP/IP networking is open to an attack known as "SYN
272 flooding". This denial-of-service attack prevents legitimate remote
274 attack and requires very little work from the attacker, who can
277 SYN cookies provide protection against this type of attack. If you
280 continue to connect, even when your machine is under attack. There
/Linux-v6.6/Documentation/admin-guide/gpio/
Dgpio-aggregator.rst23 grab and which not, reducing the attack surface.
/Linux-v6.6/fs/xfs/
DKconfig48 To close off an attack surface, say N.
75 To close off an attack surface, say N.
/Linux-v6.6/Documentation/admin-guide/LSM/
DYama.rst20 of their attack without resorting to user-assisted phishing.
/Linux-v6.6/sound/synth/emux/
Dsoundfont.c1049 int attack, hold, decay, release; in load_guspatch() local
1050 attack = calc_gus_envelope_time in load_guspatch()
1069 snd_sf_calc_parm_attack(attack); in load_guspatch()
/Linux-v6.6/Documentation/arch/x86/
Dtsx_async_abort.rst11 TSX Async Abort (TAA) is a side channel attack on internal buffers in some
Dbuslock.rst126 tolerated, but an eventual Denial of Service attack has to be prevented. It
/Linux-v6.6/drivers/firmware/efi/
DKconfig177 bool "Reset memory attack mitigation"
209 PCI devices from being able to attack the OS via DMA. However, since
/Linux-v6.6/Documentation/staging/
Dtee.rst227 There are additional attack vectors/mitigations for the kernel that should be
253 * Mitigation: The OP-TEE driver must be loaded before any potential attack
/Linux-v6.6/Documentation/userspace-api/media/v4l/
Dext-ctrls-fm-tx.rst128 Sets the attack time for audio compression feature. It is a useconds

123