I believe this is the same bug as reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003012 and upstream in https://lists.gnu.org/archive/html/bug-bash/2022-01/msg00000.html
Hmm... looks sililar. Thank you.So what should we do now? Upgrade bash from testing? Or wait until stable debian is upgraded? I am afraid of silent data corruption on production server where we use debian stable...
