Home
last modified time | relevance | path

Searched refs:SPSEL (Results 1 – 8 of 8) sorted by relevance

/trusted-firmware-m-3.6.0/docs/security/security_advisories/
Dsvc_caller_sp_fetching_vulnerability.rst34 handler code relies on the 'SPSEL' bit in 'EXC_RETURN' to get the caller stack
41 tst lr, #4 ; EXC_RETURN.SPSEL == ?
43 moveq r0, r2 ; if (EXC_RETURN.SPSEL == 0) r0 = msp;
44 movne r0, psp ; if (EXC_RETURN.SPSEL == 1) r0 = psp;
52 to the value of SPSEL. However, the code above selects secure process stack
54 handling based on EXC_RETURN.SPSEL, hence the SVC handler accesses the wrong
57 stack pointer register by checking both the PE mode and SPSEL bit. The handler
/trusted-firmware-m-3.6.0/platform/ext/cmsis/
Dcore_cm0plus.h302 uint32_t SPSEL:1; /*!< bit: 1 Stack to be used */ member
Dcore_cm4.h381 uint32_t SPSEL:1; /*!< bit: 1 Stack to be used */ member
Dcore_cm23.h327 uint32_t SPSEL:1; /*!< bit: 1 Stack-pointer select */ member
Dcore_cm33.h434 uint32_t SPSEL:1; /*!< bit: 1 Stack-pointer select */ member
Dcore_armv81mml.h441 uint32_t SPSEL:1; /*!< bit: 1 Stack-pointer select */ member
Dcore_cm55.h443 uint32_t SPSEL:1; /*!< bit: 1 Stack-pointer select */ member
Dcore_cm85.h444 uint32_t SPSEL:1; /*!< bit: 1 Stack-pointer select */ member