[Samsung Galaxy Tab A series ROMs, Kernels, Recover] Klaerchen:
I started to investigate the problem.

When I encrypt my tablet (in the state of December 2020) and do the update with the build 2021-01-14, then I also get the bootloop after entering the PIN to start Android.

Last logcat entry is:

01-30 11:18:00.231 2454 2862 I Cryptfs : Creating crypto dev "userdata"; cipher=aes-cbc-essiv:sha256, keysize=16, real_dev=/dev/block/platform/13540000.dwmmc0/by-name/USERDATA, len=11647565824, params="1 allow_discards"

And in last_kmsg it says:

<6>[ 56.062297] [4: Binder:2454_5: 2862] crypt_ctr_cipher: S/W disk encryption
<3>[ 56.063609] [4: Binder:2454_5: 2862] crypto_lookup failed due to FIPS error: eseqiv
<2>[ 56.063635] [4: Binder:2454_5: 2862] sec_debug_set_extra_info_fault = 0x13
<0>[ 56.063646] [4: Binder:2454_5: 2862] Unable to handle kernel NULL pointer dereference at virtual address 00000013
<1>[ 56.063656] [4: Binder:2454_5: 2862] pgd = ffffffc06f647000
<1>[ 56.063665] [4: Binder:2454_5: 2862] [00000013] *pgd=0000000000000000, *pud=0000000000000000
<4>[ 56.063732] [4: Binder:2454_5: 2862] ------------[ cut here ]------------
<0>[ 56.063740] [4: Binder:2454_5: 2862] Kernel BUG at ffffffc0003c3690 [verbose debug info unavailable]
<0>[ 56.063750] [4: Binder:2454_5: 2862] Internal error: Oops - BUG: 96000005 [#1] PREEMPT SMP
...
<0>[ 56.066204] [4: Binder:2454_5: 2862] Call trace:
<0>[ 56.066216] [4: Binder:2454_5: 2862] [<ffffffc0003c3690>] crypto_givcipher_default+0xe0/0x154
<0>[ 56.066226] [4: Binder:2454_5: 2862] [<ffffffc0003c37e4>] crypto_lookup_skcipher+0xe0/0xf8
<0>[ 56.066237] [4: Binder:2454_5: 2862] [<ffffffc0003c38d4>] crypto_alloc_ablkcipher+0x40/0xb0
<0>[ 56.066250] [4: Binder:2454_5: 2862] [<ffffffc0006d1458>] crypt_ctr+0x338/0x9b8
<0>[ 56.066262] [4: Binder:2454_5: 2862] [<ffffffc0006c5c70>] dm_table_add_target+0x204/0x2a8
<0>[ 56.066274] [4: Binder:2454_5: 2862] [<ffffffc0006c8dc4>] table_load+0x264/0x290
<0>[ 56.066284] [4: Binder:2454_5: 2862] [<ffffffc0006c8910>] ctl_ioctl+0x3e4/0x478
<0>[ 56.066295] [4: Binder:2454_5: 2862] [<ffffffc0006c89b8>] dm_ctl_ioctl+0x14/0x20
<0>[ 56.066308] [4: Binder:2454_5: 2862] [<ffffffc00019eab4>] do_vfs_ioctl+0x5a0/0x674
<0>[ 56.066317] [4: Binder:2454_5: 2862] [<ffffffc00019ebe8>] SyS_ioctl+0x60/0x88
<0>[ 56.066329] [4: Binder:2454_5: 2862] Code: 97fff50a 12800033 aa0003f7 b4000240 (f9401001)
<4>[ 56.066340] [4: Binder:2454_5: 2862] ---[ end trace 01299e54cab3b757 ]---
<0>[ 56.106631] [4: Binder:2454_5: 2862] Kernel panic - not syncing: Fatal exception
<0>[ 56.106631] [4: Binder:2454_5: 2862] PC is at crypto_givcipher_default+0xe0/0x154
<0>[ 56.106631] [4: Binder:2454_5: 2862] LR is at crypto_givcipher_default+0xd4/0x154
...
<0>[ 56.237913] [4: Binder:2454_5: 2862] exynos-snapshot: skip context saved(CPU:4)
<0>[ 56.237999] [4: Binder:2454_5: 2862] sec_debug: Linux version 3.18.137-g82f719e2f (wolli@MAJESTIX) (gcc version 4.9.x 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Jan 14 18:31:30 CET 2021
<0>[ 56.237999] [4: Binder:2454_5: 2862]
<0>[ 56.238023] [4: Binder:2454_5: 2862] sec_debug: rebooting...
<0>[ 56.238073] [4: Binder:2454_5: 2862] sec_reboot (0, panic)

Anyone has a good idea? ;)

Let's see, if I find a reason.