STMicroelectronics has shipped samples of the ST54M, the first secure-element member of the ST54 family — in use across Android for over a decade — that integrates dedicated hardware acceleration for post-quantum cryptography. The chip combines an NFC controller, secure element, eSIM support, and the company's K-Check PQC engine on one die. Volume production and formal certification are targeted for July 2026.

ST54M internal block diagram: NFC controller, eSIM, on-chip DC-DC converter, and secure element (Cortex-M35P) with both K-Check PQC and classical crypto engines on a single die.
FIG. 02 ST54M internal block diagram: NFC controller, eSIM, on-chip DC-DC converter, and secure element (Cortex-M35P) with both K-Check PQC and classical crypto engines on a single die. — STMicroelectronics ST54M press release, newsroom.st.com
ST54M monolithic die: four major functional blocks integrated on a single chip.
FIG. 03 ST54M monolithic die: four major functional blocks integrated on a single chip. — STMicroelectronics press release, newsroom.st.com

The K-Check accelerator runs ML-KEM (NIST FIPS 203) and ML-DSA (NIST FIPS 204), the lattice-based algorithms NIST finalized last year for key encapsulation and digital signatures. The secure element runs on an Arm Cortex-M35P core with 4.5 MB of secure nonvolatile memory and 800 kB of RAM — enough to host independent enterprise, banking, and government applets on one platform without cross-contamination. Classical cryptographic engines remain; the chip operates in hybrid mode, signing and encapsulating with both classical and post-quantum algorithms simultaneously until ecosystem migration completes.

Component / FeatureSpecification
Secure Element CoreArm Cortex-M35P
Secure Nonvolatile Memory4.5 MB
RAM800 kB
PQC AcceleratorK-Check engine
PQC AlgorithmsML-KEM (NIST FIPS 203), ML-DSA (NIST FIPS 204)
Classical CryptoECDH, ECC, RSA (hybrid mode)
ConnectivityNFC controller, eSIM
PowerIntegrated on-chip DC-DC converter
Firmware LibrariesNesLib-PQML, X-CUBE-PQC
Certifications (planned)Common Criteria 2022 EUCC, EMVCo — July 2026
Volume ProductionJuly 2026 (samples shipping now)
FIG. 04 ST54M hardware specifications and platform details — STMicroelectronics, newsroom.st.com
FeatureSpecificationNotes
CPU CoreArm Cortex-M35PSecure element processor
Secure NVM4.5 MBNon-volatile memory for applets
RAM800 kBSupports independent enterprise / banking / government applets
PQC EngineK-CheckDedicated hardware accelerator
Key EncapsulationML-KEM (NIST FIPS 203)Lattice-based; finalized 2024
Digital SignaturesML-DSA (NIST FIPS 204)Lattice-based; finalized 2024
Classical CryptoRetained (hybrid mode)ECDH / ECC run alongside PQC during migration
ConnectivityNFC + eSIMOn-die integration
On-chip DC-DCYesPreviously an external component; reduces BOM
Certification TargetJuly 2026Common Criteria 2022 EUCC + EMVCo
FIG. 05 ST54M hardware specifications and integrated PQC standards — STMicroelectronics / EE Times, eetimes.com; quantumcomputingreport.com

The harvest-now-decrypt-later scenario drives the hardware investment, not imminent quantum capability. Laurent Degauque, Connected Security Business Lines director at STMicroelectronics, said in an EE Times interview: "Someone can collect encrypted data today without being able to read it. If quantum computers break that encryption in five or six years, and those secrets remain valuable, the data is exposed." STM estimates practical cryptographic break horizon at five to seven years.

Harvest-now-decrypt-later attack: adversaries archive ciphertext today and decrypt it once quantum capability matures (STM estimates 5–7 year horizon).
FIG. 06 Harvest-now-decrypt-later attack: adversaries archive ciphertext today and decrypt it once quantum capability matures (STM estimates 5–7 year horizon). — Laurent Degauque, STMicroelectronics — EE Times interview

For edge-inference architects, the ST54M matters on two fronts. First, agent credential management: the K-Check engine offloads ML-KEM key-encapsulation from the application processor, keeping PQC operations off the inference compute budget on memory-constrained devices. Signing agent ephemeral keys or attestation certificates in hardware eliminates the side-channel exposure of software-only lattice implementations on general-purpose cores. Second, the secure element is hardened against fault-injection and side-channel monitoring at the silicon level — the same threat surface relevant for model-weight extraction and key theft on deployed edge nodes.

The chip integrates an on-chip DC-DC converter previously requiring an external component, reducing BOM count and board area. RF performance gains let OEMs use smaller and frame antennas while maintaining NFC range — directly relevant for compact edge devices where antenna real estate is constrained.

Standards readiness is the other operational gate. ML-KEM and ML-DSA are finalized, not pre-standard drafts. Degauque noted that "OEMs can now deploy solutions based on established standards." The GSMA is working on PQC-enabled eSIM specifications; devices shipping with ST54M hardware will be accelerator-ready when those standards land without a hardware respin. Common Criteria 2022 EUCC and EMVCo certification evaluations are complete; formal certification is scheduled July 2026, the gate for payment-network and government-identity deployments.

AlgorithmNIST StandardCryptographic FamilyPurposeStatus
ML-KEMFIPS 203Lattice-based (Module-Lattice)Key Encapsulation / Key ExchangeFinalized 2024
ML-DSAFIPS 204Lattice-based (Module-Lattice)Digital Signatures / AttestationFinalized 2024
FIG. 07 NIST-finalized post-quantum algorithms implemented in the ST54M K-Check engine — NIST FIPS 203 / FIPS 204; STMicroelectronics ST54M press release

Hybrid mode is transitional, not permanent. Running ML-KEM alongside ECDH doubles key-agreement overhead on the wire, and managing dual certificate chains adds complexity to PKI pipelines most edge deployments have not encountered. Firmware libraries NesLib-PQML and X-CUBE-PQC are available for ST54M, but integrating them into existing secure-enclave provisioning flows requires explicit engineering effort.

Hybrid-mode key agreement: ST54M runs ECDH (classical) and ML-KEM (post-quantum) simultaneously, combining both shared secrets until ecosystem migration to PQC-only is complete.
FIG. 08 Hybrid-mode key agreement: ST54M runs ECDH (classical) and ML-KEM (post-quantum) simultaneously, combining both shared secrets until ecosystem migration to PQC-only is complete. — STMicroelectronics ST54M documentation; EE Times interview with Laurent Degauque
Hybrid mode operation: the ST54M runs classical (ECDH/ECC) and post-quantum (ML-KEM/ML-DSA) engines in parallel, producing a combined key bundle during the ecosystem migration period.
FIG. 09 Hybrid mode operation: the ST54M runs classical (ECDH/ECC) and post-quantum (ML-KEM/ML-DSA) engines in parallel, producing a combined key bundle during the ecosystem migration period. — STMicroelectronics / EE Times, eetimes.com

Architects with long-lived agent credentials or model attestation keys signed today with RSA or ECC should treat those as already harvested if the agent's operational life exceeds five years. Hardware that can re-issue those keys under ML-DSA without a board revision is the minimum viable mitigation. The ST54M's sampling availability means the design cycle can start now.