BitLocker suspended by hotpatch update (possibly KB5123607)

Anyone noticed that something suspended BitLocker during the August updates rollout?

My No.1 suspect is KB5123607 because it's linked to the TPM.

The issue with this is that our users can go for up to a month without restarting naturally under the hotpatch updates model. So, triggering a BitLocker suspension without requesting a restart seems incredibly risky. It was basically a gamble that a restart would happen before anything bad could happen.

It led to our automated non-compliance emails being sent to users that were already on a lengthy delay designed to avoid transient errors.

Today, it possibly took another turn. One of our kiosk-type devices booted into Recovery mode. Restarting again returned the device to normal. No requirement to enter the BitLocker recovery key (which was not requested anyway).