drivers/tee/amdtee

AMD Secure Processor Trusted Execution Environment (AMD-TEE)

A kernel interface to the trusted execution environment hosted on AMD's Platform Security Processor (also called the AMD Secure Processor), the dedicated security coprocessor embedded in modern AMD client and server CPUs. It lets userspace load and call trusted applications running in the secure world on Ryzen PRO laptops, desktops, and EPYC servers.

keep conf=0.88 deploy=low replacement=none subsystem=tee category=crypto
88%

recommendation

It should stay in the kernel because the AMD Secure Processor is built into current Ryzen PRO and EPYC CPUs that are still being sold in 2025, and the code itself is actively maintained, with AMD engineers posting targeted fixes as recently as March 2026. Real-world use of the TEE path is niche, but the hardware substrate is mainstream and the driver is the only Linux gateway to it.

repository signals

7 files
1,415 source lines
14 commits, 5y
+203 / −129 lines added / removed, 5y
9 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 14 total · active in 11/61 months
2021 2022 2023 2024 2025 2026 2021-04: 1 commit · +106 −16 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: 1 commit · +2 −3 2021-12: 0 commits · +0 −0 2022-01: 0 commits · +0 −0 2022-02: 2 commits · +17 −40 2022-03: 0 commits · +0 −0 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: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 0 commits · +0 −0 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 1 commit · +14 −15 2023-03: 1 commit · +2 −2 2023-04: 0 commits · +0 −0 2023-05: 1 commit · +23 −17 2023-06: 0 commits · +0 −0 2023-07: 0 commits · +0 −0 2023-08: 0 commits · +0 −0 2023-09: 1 commit · +6 −4 2023-10: 0 commits · +0 −0 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 0 commits · +0 −0 2024-02: 0 commits · +0 −0 2024-03: 1 commit · +4 −5 2024-04: 0 commits · +0 −0 2024-05: 0 commits · +0 −0 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: 0 commits · +0 −0 2024-11: 0 commits · +0 −0 2024-12: 0 commits · +0 −0 2025-01: 0 commits · +0 −0 2025-02: 0 commits · +0 −0 2025-03: 0 commits · +0 −0 2025-04: 2 commits · +9 −7 2025-05: 0 commits · +0 −0 2025-06: 0 commits · +0 −0 2025-07: 0 commits · +0 −0 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: 1 commit · +4 −4 2026-02: 2 commits · +16 −16 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    Upstream activity is current: amdtee received a targeted functional patch in March 2026, so there is no sign of abandonment or removal.

  2. amd.com

    AMD states current AMD PRO platforms include an 'AMD Secure Processor', indicating the underlying security processor family is still present in newly sold CPUs.

  3. amd.com

    AMD's EPYC server line was actively marketed as current in 2024-2025 with built-in security features, supporting that PSP-backed platforms remain in new deployments.

codex reasoning notes (technical)

Local inspection via exec_command showed this is a real TEE driver wired to PSP interfaces (`psp-tee.h`, `psp_check_tee_status()`) and Kconfig names it 'AMD-TEE'. lore_file_timeline on `drivers/tee/amdtee/core.c` returned activity through 2026-03-27, including a non-treewide amdtee patch at the cited lore URL; histogram shows recurring touches across 2024-2026, so removal/deprecation is not supported. A lore_regex removal-search timed out and a fallback `lei q` attempt was blocked by local daemon permissions, so removal-talk confidence is inferred from the positive activity signal rather than a dedicated thread hit. Web search returned AMD PRO Technologies and EPYC product pages showing the AMD Secure Processor on current product lines, so the hardware class is still sold new in 2025. Deployment is rated low rather than medium/high because this is a niche secure-world/TEE path even though the CPU family itself is current.