Altera Trusted Firmware CVE-2026-13465

Requires local, high-privileged execution on the Altera SoC FPGA Hard Processor System (HPS) - realistically control of the non-secure/rich OS (e.g., root or kernel on the ARM cores) that can invoke the secure-monitor interface into Trusted Firmware. Exploitation is limited by the need for that pre-existing privileged foothold (PR:H, AV:L, no remote/network path) and by the narrow deployment: only devices running the Altera SoCFPGA Trusted Firmware port up to and including socfpga_v2.14.0 are affected. No user interaction is required (UI:N). This is a privilege/trust-boundary escalation into the secure world, not a remotely exploitable default-configuration flaw.

This is a genuine but access-gated risk. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:H/UI:N) confirms a LOCAL attack vector requiring HIGH privileges, so this is not a remotely-reachable, low-effort flaw - the attacker must already hold a privileged foothold on the Hard Processor System (typically the rich/non-secure OS kernel making SMC calls into secure firmware). What makes it serious despite the local vector is where the corruption lands: Trusted Firmware runs in the secure world (ARM EL3/monitor), so a stack overflow there crosses a trust boundary. This is reflected in the subsequent-system metrics (SC:L/SI:H/SA:H) and vendor score of 8.3 (HIGH). No EPSS score, KEV listing, or POC was provided in the intelligence, and the only reference is the vendor's own advisory (Altera asa-0006), meaning there is no independent signal of active or imminent exploitation - this reads as a vendor-disclosed hardening issue, not an in-the-wild threat. Net: prioritize for affected SoC FPGA fleets because the impact (secure-world integrity/availability compromise) is high, but the PR:H gate and niche footprint mean it is targeted/embedded-device risk rather than mass-exploitation risk.

An attacker who has already achieved privileged code execution in the non-secure world (e.g., compromised Linux kernel/root on the HPS) issues a crafted request across the secure-monitor interface into Altera Trusted Firmware, overflowing a stack buffer in the EL3 secure firmware. This corrupts secure-world control flow, enabling code execution or a persistent denial of the secure services the platform depends on. No public exploit code was identified at time of analysis, and the local, high-privilege prerequisite makes this a post-compromise escalation rather than an initial-access vector.