dm-integrity authenticated encryption support for block devices is part of the Linux kernel since version 4.12.
If it's enabled in your kernel then it should be automatically loaded, when needed.
You can check if your kernel has this feature enabled by verifying its config, for example on a Fedora system:
$ grep DM_INTEGRITY /boot/config-4.17.12-100.fc27.x86_64
Here it's compiled as a module.
Then check if the module is actually available, e.g.:
$ find /usr -name 'dm-integrity.ko*'
If it's not available you can query which package provides that file, e.g. something like:
$ apt-file search 'dm-integrity.ko*' # on Debian
$ dnf provides '*dm-integrity.ko*' # on Fedora
Note that (as of cryptsetup 2.0) the authenticated encryption support is marked as experimental. Also, the release notes warn about using
DO NOT USE in production! The GCM mode uses only 96-bit nonce, and possible collision means fatal security problem.
It's thus better to use one of the other examples from the release notes:
# cryptsetup luksFormat --type luks2 <device> --cipher aes-xts-plain64 \
# cryptsetup luksFormat --type luks2 <device> --cipher chacha20-random \
Finally, the release notes caution:
There will be better suitable authenticated modes available soon For now we are just preparing framework to enable it (and hopefully improve security of FDE). FDE authenticated encryption is not a replacement for filesystem layer authenticated encryption. The goal is to provide at least something because data integrity protection is often completely ignored in today systems.