With NVMe in Linux, device names are like /dev/nvmeXnY where X is the NVMe device number, and Y is the namespace number. When partitioned, there is a third number: device names for NVMe partitions are of the form /dev/nvmeXnYpZ where Z is the partition number.

The namespace number is essentially for enterprise-grade hardware only: for consumer-grade NVMe drives, usually only one namespace is supported, and thus the namespace number will always be 1.

So: if you run fdisk -l /dev/nvme0n1, does it list any partitions?

If there are no partitions visible at all, Bitlocker might be using the NVMe drive's built-in hardware encryption support, which could make recovery trickier. It might be that only a real Windows system can extract the hardware encryption passphrase/key from the Bitlocker recovery key.

But if fdisk can list the partitions, then something like dislocker could be used to unlock the encryption and make the NTFS filesystem(s) mountable.

See also this question at SuperUser.SE for a lot of information on accessing a Bitlocker-encrypted drives on Linux.

sedutil-cli is a Linux tool which can be used to lock/unlock drives that have Opal-compliant hardware encrypting functionality, but unfortunately that tool doesn't know how to use a Bitlocker recovery key for unlocking a hardware-encrypted drive. You can read the linked page to gain an understanding of what is going on, and you could use the sedutil-cli tool to check if your drives have the hardware encryption feature and if it is currently locked or not.

But if Bitlocker is using the hardware encryption feature, then as far as I know, sedutil-cli alone cannot unlock the drive; you'll need to plug the drive as a second drive to a working Windows system that supports Bitlocker, and then supply the recovery key when Windows asks for it.

With NVMe in Linux, device names are like /dev/nvmeXnY where X is the NVMe device number, and Y is the namespace number. When partitioned, there is a third number: device names for NVMe partitions are of the form /dev/nvmeXnYpZ where Z is the partition number.

The namespace number is essentially for enterprise-grade hardware only: for consumer-grade NVMe drives, usually only one namespace is supported, and thus the namespace number will always be 1.

So: if you run fdisk -l /dev/nvme0n1, does it list any partitions?

If there are no partitions visible at all, Bitlocker might be using the NVMe drive's built-in hardware encryption support, which could make recovery trickier. It might be that only a real Windows system can extract the hardware encryption passphrase/key from the Bitlocker recovery key.

But if fdisk can list the partitions, then something like dislocker could be used to unlock the encryption and make the NTFS filesystem(s) mountable.

See also this question at SuperUser.SE for a lot of information on accessing a Bitlocker-encrypted drives on Linux.

sedutil-cli is a Linux tool which can be used to lock/unlock drives that have Opal-compliant hardware encrypting functionality, but unfortunately that tool doesn't know how to use a Bitlocker recovery key for unlocking a hardware-encrypted drive. You can read the linked page to gain an understanding of what is going on, and you could use the sedutil-cli tool to check if your drives have the hardware encryption feature and if it is currently locked or not.

But if Bitlocker is using the hardware encryption feature, then as far as I know, sedutil-cli alone cannot unlock the drive; you'll need to plug the drive as a second drive to a working Windows system that supports Bitlocker, and then supply the recovery key when Windows asks for it.

Since you apparently can see at least one partition with fdisk -l /dev/nvme0n1, you should try using dislocker with that partition /dev/nvme0n1p1. You'll need to specify a mount point for dislocker, and it will create a virtual filesystem which will contain an unencrypted NTFS filesystem image you can mount.

In other words, if you do:

mkdir /mnt/bitlocker
dislocker -p <Bitlocker recovery key> -V /dev/nvme0n1p1 /mnt/bitlocker
mkdir /mnt/unencrypted
mount -o loop /mnt/bitlocker/dislocker-file /mnt/unencrypted

... then you should be able to access the encrypted partition at /mnt/unencrypted/.