When the card table is resized (for example committing space for the card table at
initiation) the guard card at the end of the card table can be overwritten due to
rounding up for page alignment and a commit_memory() call over the region including
the guard card.
This affects assertion checking and verification of the card table. It does not
affect the product builds unless verification is being used.
When resize_covered_region() is called, a call to commit_memory() can result
where the region passed to commit_memory() includes the guard card. The guard
card is cleared of the last_card value as a side effect of the commit_memory().