Lines Matching refs:SMC

6 |                | Normal World SMC client to another                          |
15 | Configurations | Multiple normal world SMC clients calling into AArch64 BL31 |
18 | Impact         | Leakage of SMC return values from one normal world SMC      |
28 into the firmware. However, for an SMC exception, the general purpose registers
31 As per the `SMC Calling Convention`_, up to 4 values may be returned to the
52 In the case of an SMC handler that does not use all 4 return values, the
54 ``restore_gp_registers()`` restores the stale values saved by a previous SMC
57 In the presence of multiple normal world SMC clients, this behaviour might leak
59 client first sends an SMC that returns 4 values, a malicious client may then
60 send a second SMC expecting no return values (for example, a
61 ``SDEI_EVENT_COMPLETE`` SMC) to get the 4 return values of the victim client.
64 multiple normal world SMC clients lies with EL2 software.  When present, EL2
65 software must trap SMC calls from EL1 software to ensure secure behaviour.
68 SMC synchronous exception. It has behaved this way since the first version.
81 Note that AArch32 TF-A is not affected by this issue. The SMC handling code in
90      * spsr, lr, sp registers and the `scr` register to the SMC context on entry
91      * due a SMC call. The `lr` of the current mode (monitor) is expected to be
97         /* Save r0 - r12 in the SMC context */