That sounds weird. Can you reproduce the problem by transaction-update of a single kernel package 6.8.2?