Yes, I also saw the comment by @philm , albeit only an hour ago.
Kernel 6.7 would seem to solve similar issues for some. Perhaps reverting to 6.1 and waiting for 6.7 to reach Stable is a valid option for those also affected.
Further to that otherwise possible workaround, I note this additional comment from Philm: Kernel 6.1.66-1 is also affected a minute or two ago.