Might be a dup of bug 1208939, and due to the lockdown introduced with kernel 6.1.2 if booted in secure boot mode.