If you use BitLocker similarly to how you use VeraCrypt, this vulnerability does not affect you.
The most common mode for Bitlocker is the automatic mode, where the drive is encrypted and Windows loads the key at boot time without any interaction. It's transparent to the user, most people probably don't even know it's enabled. It uses the computer's TPM to store the key, which is only released when Secure Boot confirms that the OS has not been tampered with.
It stops an attacker accessing files by booting Linux or removing the drive, or at least it is supposed to. The idea is that if you don't know the Windows password, you can't log in to access anything, but as this guy discovered you can just go into the recovery environment which doesn't need a user account. The drive is unlocked at boot as normal.
It does seem to be some kind of massive screw up at the very least. Windows 10 made you log in for the recovery environment, but for some reason it changed with 11.
If you set a BitLocker password that needs to be entered at boot, similar to how VeraCrypt works, this bypass doesn't work.