During a live update, the state record for a Xenstore watch with a specified watch depth is written with two bytes missing. This leads to an inconsistent state when the new Xenstore reads the state back, which can result in a crash or the retrieval of incorrect data.