So, I've used Kernel 6.15.0 since the day it was released until 2 days ago. In all that time the issue didn't happen once. Two days ago I went back to 6.12.32-1 from the repos and it just happened to me just now. So either the fix of the issue was introduced at some point between the release of 6.14.5 and 6.15, as 6.14.5 was the lastest version I used that showed this issue, or at least something was changed that made this issue appear a lot less frequent.
Best regards Richard
