Lines Matching refs:or
26 - Not covering advanced or invasive physical attacks such as decapsulation,
48 | DF1 | SP to SPMC communication. FF-A function invocation or |
60 | | LSP can send direct response SP1 or NWd through SPMC. |
111 NS-EL2 (Hypervisor) or NS-EL1 (VM or OS kernel).
114 such as bus probing or DRAM stress.
131 analysis is evaluated based on the environment being ``Server`` or ``Mobile``.
225 | | driver, or Hypervisor although it remains untrusted|
262 | | PARTITION_INFO_GET or memory sharing primitives. |
277 | Threat | **An endpoint may tamper with its own state or the |
282 | | - its own or another SP state by using an unusual |
283 | | combination (or out-of-order) FF-A function |
292 | | requests and responses, or handling of interrupts|
293 | | This can be led by random stimuli injection or |
330 | | a matter of triggering a malfunction or extracting |
335 | | getting access or gaining permissions to a memory |
367 | | or state information by the use of invalid or |
370 | | Lack of input parameter validation or side effects |
396 | | The use of software (canaries) or hardware |
415 | | The secure partition or SPMC replies to a partition|
426 | Assets | SPMC or SP state |
445 | | prevent its internal state or the state of an SP |
461 | | extract the traffic between an SP and the SPMC or |
485 | | hardware countermeasures at platform or chip level.|
495 | | state or secrets by the use of software-based cache|
503 | Assets | SP or SPMC state |
613 | | share, lend, relinquish or reclaim unauthorized |