Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-48507: CWE-1284 Improper Validation of Specified Quantity in Input in AMD Kria™ SOM

0
High
VulnerabilityCVE-2025-48507cvecve-2025-48507cwe-1284
Published: Sun Nov 23 2025 (11/23/2025, 17:07:56 UTC)
Source: CVE Database V5
Vendor/Project: AMD
Product: Kria™ SOM

Description

The security state of the calling processor into Arm® Trusted Firmware (TF-A) is not used and could potentially allow non-secure processors access to secure memories, access to crypto operations, and the ability to turn on and off subsystems within the SOC.

AI-Powered Analysis

AILast updated: 11/23/2025, 17:23:22 UTC

Technical Analysis

CVE-2025-48507 is a vulnerability classified under CWE-1284, indicating improper validation of specified quantity in input, specifically relating to the security state of the calling processor within Arm® Trusted Firmware (TF-A) on AMD's Kria™ System on Module (SOM). The core issue is that the firmware does not properly verify whether the calling processor is operating in a secure or non-secure state before granting access to sensitive resources. This flaw can allow a non-secure processor to bypass security boundaries and gain unauthorized access to secure memory regions, cryptographic operations, and the ability to enable or disable subsystems within the System on Chip (SOC). The vulnerability requires local access with low privileges and some user interaction, as indicated by the CVSS vector (AV:L/AC:L/AT:N/PR:L/UI:P). The impact on confidentiality, integrity, and availability is high, as unauthorized access to secure memory and crypto operations can lead to data leakage, manipulation of cryptographic functions, and disruption of SOC components. Although no exploits are currently known in the wild, the potential for severe damage exists, especially in environments relying on the Kria™ SOM for secure embedded or edge computing tasks. The affected versions are not yet specified, but the vulnerability has been officially published and assigned a CVSS 4.0 score of 8.6, reflecting its critical nature. The vulnerability stems from a fundamental flaw in the validation logic within the trusted firmware, which is a critical component in enforcing the security model of the SOC. This issue highlights the importance of rigorous input validation and security state verification in trusted execution environments.

Potential Impact

For European organizations, the impact of CVE-2025-48507 can be significant, particularly for those deploying AMD Kria™ SOM in embedded systems, industrial control, telecommunications, and defense sectors. Unauthorized access to secure memory and cryptographic operations can lead to exposure of sensitive data, including encryption keys and proprietary information. The ability to control SOC subsystems could allow attackers to disrupt critical operations, cause denial of service, or manipulate system behavior, undermining trust in embedded devices. This is especially critical in sectors such as automotive, aerospace, and critical infrastructure, where embedded modules like Kria™ SOM are increasingly used. The vulnerability could facilitate lateral movement within networks if exploited on edge devices, potentially impacting broader IT and OT environments. Given the high severity and the nature of the flaw, organizations face risks of intellectual property theft, operational disruption, and compliance violations under regulations like GDPR if personal data confidentiality is compromised.

Mitigation Recommendations

To mitigate CVE-2025-48507, European organizations should: 1) Monitor AMD's official channels for patches or firmware updates addressing this vulnerability and apply them promptly once available. 2) Implement strict access controls to limit local access to devices running Kria™ SOM, including physical security measures and role-based access controls. 3) Employ runtime integrity monitoring and anomaly detection on embedded devices to identify unusual access patterns to secure memory or cryptographic functions. 4) Segment networks to isolate vulnerable embedded systems from critical infrastructure and sensitive data environments. 5) Conduct thorough security audits of devices incorporating Kria™ SOM to identify potential exploitation attempts. 6) Collaborate with vendors and supply chain partners to ensure secure firmware versions are deployed. 7) Educate operational technology and embedded system teams about the risks and signs of exploitation related to this vulnerability. These steps go beyond generic advice by focusing on firmware patching, access restriction, monitoring, and supply chain security specific to embedded SOC environments.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
AMD
Date Reserved
2025-05-22T16:34:02.896Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 692342efa8cb427b79e69085

Added to database: 11/23/2025, 5:22:55 PM

Last enriched: 11/23/2025, 5:23:22 PM

Last updated: 11/23/2025, 7:52:39 PM

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats