Lines Matching full:or

21 processing or storing.
33 intended to reduce the attack surface or elevate the cost of an attack within
38 who is able to grant or deny various types of permissions that may affect how
39 users benefit from available resources, or the level of confidentiality of
40 their activities. Administrators may also delegate all or part of their own
47 suit their expectations (relax or restrict).
60     UNIX domain sockets or other IPC mechanisms).
61   * network communications within the same or with other systems
69     affect the system's availability (shutdown, reboot, panic, hang, or making
80 initial user namespace, such as changing time, loading modules or mounting
118     documented as lowering the security level (e.g. ``CONFIG_NOMMU``), or
124     unprivileged users, or reduce the kernel's ability to enforce some
125     protections or mitigations. Example: write access to procfs or debugfs.
127   * issues triggered only when using features intended for development or
136     using any subsystem marked as experimental or not intended for production
139   * running out-of-tree modules or unofficial kernel forks; these should be
145     perform that action or modify that state (e.g. ``CAP_SYS_ADMIN``,
160   conditions with zero system noise, or those requiring an unrealistic number
165     environment (such as IP ID, TCP ports or sequence numbers that can only be
173     impact on the system makes it unlikely or impossible to remain undetected
176   * problems seen only under development simulators, emulators, or combinations
179     unrealistic CPU frequencies, RAM sizes or disk capacities, network speeds).
183     emulator only to retrieve 7 uninitialized bytes in a structure, or
190     demonstrable exploit path (e.g. ASLR bypass, events timing or probing with
200   and that cannot be chosen by the attacker, or face access restrictions:
202   * structure padding reported by syscalls or other interfaces.
213   Drivers are implemented against a specification. When a device or a storage
219   * bugs triggered by mounting a corrupted or maliciously crafted file system
222     issues that are resolved, mitigated, or detected by running a filesystem
225   * bugs whose reproduction requires hardware modification or emulation,
226     including fake USB devices that pretend to be another one, or devices
231   Issues that require physical access to the machine, hardware modification, or