The targetOpTimeCB callback captures the lock by reference, however this callback is run in a future chain, when it is executed, this lock can no longer be valid.

When we call those functions to fulfill the a replication waiter's promise, the targetOpTimeCB callback will be executed by the same thread, but this thread holds a different lock than the one targetOpTimeCB captured.

This is caused by SERVER-90314. Prior to SERVER-90314, this was not an issue because we were not passing WithLock explicitly everywhere so no need to capture the lock.