You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a key in a secure element, if the call to the secure element's create method succeeds, but an error happens later (e.g. saving the driver's persistent data to storage), the API function reports a failure, but the key remains in the secure element. This is a resource leak and can be a data leak (when importing a key).
There may be other key creation errors that are not handled properly. This should be reviewed and tested.
Issue request type
[ ] Question
[ ] Enhancement
[x] Bug
The text was updated successfully, but these errors were encountered:
This issue only concerns dynamically registered secure element drivers enabled with MBEDTLS_PSA_CRYPTO_SE_C, which are deprecated. We do not intend to do any further work on that feature, even bug fixes, unless we have reports of it being used in the wild.
Description
When creating a key in a secure element, if the call to the secure element's create method succeeds, but an error happens later (e.g. saving the driver's persistent data to storage), the API function reports a failure, but the key remains in the secure element. This is a resource leak and can be a data leak (when importing a key).
There may be other key creation errors that are not handled properly. This should be reviewed and tested.
Issue request type
The text was updated successfully, but these errors were encountered: