To be fair, it was just a bug in 6.1.64, which was already fixed in 6.1.66. Both are "old" kernels, so it's nothing to worry about, unless you were deliberately staying on 6.1 for some odd reason (yes, I'm aware 6.1 is LTS, but so is 6.6).