| Previous | Next |
| TPM_E_DEFEND_LOCK_RUNNING | TPM_20_E_OBJECT_MEMORY |
TPM_20_E_CONTEXT_GAP
Context blobs have an allowed sequence window
TPM_20_E_CONTEXT_GAP wraps the warning TPM_RC_CONTEXT_GAP. Saved TPM contexts carry sequence information. To limit replay and bound internal tracking, the TPM allows only a finite gap between the oldest reloadable saved context and the current context counter. A context kept too long while many newer contexts are saved can fall outside that window.
The blob is not necessarily corrupted. It may be cryptographically valid yet stale relative to later context activity. Retrying the identical ContextLoad cannot make the gap smaller.
Operational implications
- Avoid retaining large numbers of saved session or object contexts while continually creating newer ones.
- Let the operating-system resource manager virtualize TPM resources instead of persisting raw blobs indefinitely.
- When possible, recreate the transient object from its public/private material or start a fresh authorization session.
- Do not treat a saved context file as a durable key backup; its lifetime and replay rules differ from persistent TPM objects.
References
- TCG Part 1: saved-context protection and gap handling
- TCG Part 2: TPM_RC_CONTEXT_GAP
- tpm2-tools: context object format
Looking for a different code? Search another status or error code.