If you can do that, could you try if downgrading the following packages to before version 2:2.6.1-5 fixes your problem:
* cryptsetup
* cryptsetup-bin
* cryptsetup-initramfs
* libcryptsetup12
For example, I’m currently on 2:2.6.1-4~deb12u1 and do not have this issue. Do you have an internet connection when booting from sd-card?
After mounting your encrypted rootfs, mount your /boot partition into that as well. Also don’t forget to mount proc, dev and sys. Assuming you mounted your rootfs to /mnt you can run:
mount -o bind /dev /mnt/dev
mount -t sysfs sys /mnt/dev
mount -t proc proc /mnt/proc
mount /dev/mmcblk0p1 /mnt/boot
After that you can chroot /mnt to carry out tasks in your broken system. For example it would maybe be useful to see the last things you installed with apt. You can find those at the bottom of /var/log/apt/history.log. There we can see which packages changed in your last upgrade that broke your system. That will be very useful to have.