808bits

Samsung Kernel Cryptographic Module

FIPS 140-3 certificate #4764 · Samsung Electronics Co., Ltd. · data as of 2026-08-28
Historical. Replaced by certificate #5253. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: Interim Validation. When operated in approved mode

Certificate

Certificate number4764
StandardFIPS 140-3
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorSamsung Electronics Co., Ltd. · website
Software versions2.3

Module description

Provides general purpose cryptographic services to services in the Linux kernel and user-space applications, intended to protect data in transit and at rest.

Security level exceptions

  • Physical security: N/A
  • Non-invasive security: N/A
  • Mitigation of other attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES-CBCA3242
AES-ECBA3242
HMAC-SHA-1A3242
HMAC-SHA2-224A3242
HMAC-SHA2-256A3242
HMAC-SHA2-384A3242
HMAC-SHA2-512A3242
SHA-1A3242
SHA2-224A3242
SHA2-256A3242
SHA2-384A3242
SHA2-512A3242

Tested configurations

  • Kernel 5.15 running on Samsung Galaxy S23 with Qualcomm Snapdragon 8 Gen 2 with PAA, Kernel 5.15 running on Samsung Galaxy S23 with Qualcomm Snapdragon 8 Gen 2 without PAA, Linux Kernel 5.15 running on Samsung Tab Active5 with Samsung Electronics Exynos 1380 with PAA, Linux Kernel 5.15 running on Samsung Tab Active5 with Samsung Electronics Exynos 1380 without PAA, Linux Kernel 5.15 running on Samsung Galaxy Tab S9 FE with Samsung Electronics Exynos 1380 with PAA, Linux Kernel 5.15 running on Samsung Galaxy Tab S9 FE with Samsung Electronics Exynos 1380 without PAA

Validation history

DateTypeLab
2024-08-16InitialGossamer Security Solutions
2025-07-09UpdateGossamer Security Solutions
2025-09-08UpdateGossamer Security Solutions

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: 2024-08-16

Source documents