linux-drivers/
drivers/crypto/stm32

STMicroelectronics STM32 CRYP and HASH crypto accelerators

Hardware AES, DES/3DES, and SHA/HMAC acceleration blocks built into STMicroelectronics STM32 microcontrollers and microprocessors, including the STM32F7 series and the Linux-capable STM32MP1 and STM32MP13 application processors widely used in industrial, IoT, and embedded gateway products.

keep conf=0.89 deploy=medium replacement=none subsystem=crypto category=crypto
89%

recommendation

It should stay in the kernel because the hardware is built into STMicroelectronics' STM32 microcontroller and microprocessor families that are actively shipping in 2025, and the driver itself is still receiving upstream patches as recently as March 2026. Because the crypto block is SoC-specific silicon, no other driver can replace it for these chips.

repository signals

4 files
5,328 source lines
63 commits, 5y
+3,360 / −2,276 lines added / removed, 5y
21 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 63 total · active in 19/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 0 commits · +0 −0 2021-07: 0 commits · +0 −0 2021-08: 0 commits · +0 −0 2021-09: 0 commits · +0 −0 2021-10: 0 commits · +0 −0 2021-11: 9 commits · +404 −583 2021-12: 2 commits · +7 −6 2022-01: 0 commits · +0 −0 2022-02: 0 commits · +0 −0 2022-03: 1 commit · +3 −1 2022-04: 0 commits · +0 −0 2022-05: 0 commits · +0 −0 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 0 commits · +0 −0 2022-09: 1 commit · +2 −2 2022-10: 0 commits · +0 −0 2022-11: 0 commits · +0 −0 2022-12: 2 commits · +324 −93 2023-01: 5 commits · +238 −65 2023-02: 0 commits · +0 −0 2023-03: 9 commits · +173 −222 2023-04: 0 commits · +0 −0 2023-05: 0 commits · +0 −0 2023-06: 0 commits · +0 −0 2023-07: 10 commits · +574 −163 2023-08: 2 commits · +459 −392 2023-09: 0 commits · +0 −0 2023-10: 4 commits · +10 −43 2023-11: 0 commits · +0 −0 2023-12: 2 commits · +2 −2 2024-01: 0 commits · +0 −0 2024-02: 0 commits · +0 −0 2024-03: 0 commits · +0 −0 2024-04: 1 commit · +448 −122 2024-05: 4 commits · +674 −45 2024-06: 0 commits · +0 −0 2024-07: 0 commits · +0 −0 2024-08: 0 commits · +0 −0 2024-09: 0 commits · +0 −0 2024-10: 2 commits · +4 −4 2024-11: 0 commits · +0 −0 2024-12: 0 commits · +0 −0 2025-01: 0 commits · +0 −0 2025-02: 2 commits · +18 −18 2025-03: 0 commits · +0 −0 2025-04: 0 commits · +0 −0 2025-05: 0 commits · +0 −0 2025-06: 1 commit · +0 −490 2025-07: 2 commits · +1 −3 2025-08: 0 commits · +0 −0 2025-09: 0 commits · +0 −0 2025-10: 0 commits · +0 −0 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 2 commits · +16 −19 2026-02: 2 commits · +3 −3 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    stm32-hash saw an upstream patch in March 2026, indicating current maintenance activity rather than abandonment.

  2. lore.kernel.org

    stm32-cryp saw an upstream patch in March 2026, indicating current maintenance activity rather than abandonment.

  3. st.com

    STM32F756 remains an active, volume-production MCU and advertises hardware crypto including HASH/HMAC and cryptographic acceleration.

  4. st.com

    STM32MP135F remains an active, volume-production MPU with secured cryptographic acceleration and HASH/HMAC hardware.

  5. st.com

    STM32MP1-series products were still listed by ST with secure boot and cryptography options, supporting ongoing Linux-class embedded deployments.

codex reasoning notes (technical)

Local shell `rg` on the driver sources shows active platform-driver code for STM32 CRYP and HASH, with compatibles including stm32f756, stm32mp1, and stm32mp13. `lore_file_timeline` on both C files returned fresh 2026 linux-crypto traffic and no sign of removal-oriented history, so this is an actively maintained embedded SoC driver, not a legacy orphan. ST product URLs were obtained via web search and show relevant STM32 families still active/in production in 2025-2026, so hardware is still sold new. Deployment is medium: real in industrial/IoT/embedded Linux and MCU products, but not broad general-purpose computing. No natural upstream replacement driver exists because this is SoC-specific crypto IP.