808bits

Red Hat Enterprise Linux Kernel Crypto API Cryptographic Module v4.0

FIPS 140-2 certificate #2742 · Red Hat®, Inc. · data as of 2026-08-28
Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode with modules Red Hat Enterprise Linux NSS Cryptographic Module v4.0 validated to FIPS 140-2 under Cert. #2711 operating in FIPS mode and Red Hat Enterprise Linux Libreswan Cryptographic Module v4.0 validated to FIPS 140-2 under Cert. #2721 operating in FIPS mode. The module generates random strings whose strengths are modified by available entropy

Certificate

Certificate number2742
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorRed Hat®, Inc. · website
Software versions4.0

Module description

The Linux kernel Crypto API implemented in Red Hat Enterprise Linux 7.1 provides services operating inside the Linux kernel with various ciphers, message digests and an approved random number generator.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES3567, 3568, 3569, 3571, 3572, 3573, 3574, 3575, 3590, 3592
DRBG911, 912, 913, 914, 915, 917, 924, 926
HMAC2273, 2274, 2275, 2277
RSA1835, 1836, 1837, 1839
SHS2935, 2936, 2937, 2939
Triple-DES1988, 1989

Other algorithms

DES; PRNG; SHS (non-compliant)

Tested configurations

  • Red Hat Enterprise Linux 7.1 running on HP ProLiant DL380p Gen8 with PAA
  • Red Hat Enterprise Linux 7.1 running on HP ProLiant DL380p Gen8 without PAA
  • Red Hat Enterprise Linux 7.1 running on IBM POWER8 Little Endian 8286-41A (single-user mode)

Validation history

DateTypeLab
2016-09-12Initialatsec information security corporation

Status timeline

As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.

  • 2026-08-21: first observed by this tracker, status historical
  • Validation dates on record: 2016-09-12

Source documents