Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-62818 is a critical-severity Out-of-bounds Write (CWE-787) vulnerability in Samsung Exynos 990 Firmware. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-62818 is a high-severity vulnerability affecting multiple Samsung processors and modems, including Mobile Processor and Wearable Processor Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, 2500, 9110, W920, W930, W1000, as well as Modem 5123, 5300, and 5400. The issue stems from an out-of-bounds write (CWE-787) triggered by a mismatch between the TP-UDHI and UDL values during processing of an SMS TP-UD packet. It carries a CVSS v3.1 base score of 9.8, indicating critical risk due to its network accessibility, low attack complexity, and lack of required privileges or user interaction.
Attackers can exploit this vulnerability remotely over the network by sending a specially crafted SMS message to a targeted device. No authentication or physical access is needed, enabling unauthenticated remote exploitation. Successful exploitation leads to high-impact consequences, including arbitrary code execution, data corruption, or device denial of service through the out-of-bounds write, compromising confidentiality, integrity, and availability.
Samsung has addressed this vulnerability through product security updates detailed on their semiconductor support pages, including a dedicated CVE advisory at https://semiconductor.samsung.com/support/quality-support/product-security-updates/cve-2025-62818/ and the general updates portal at https://semiconductor.samsung.com/support/quality-support/product-security-updates/. Security practitioners should verify affected devices and apply the latest firmware or processor patches promptly.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-209268
Vulnerability Data
An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, 2500, 9110, W920, W930, W1000, Modem 5123, Modem 5300, and Modem 5400. An out-of-bounds write…
more
occurs due to a mismatch between the TP-UDHI and UDL values when processing an SMS TP-UD packet.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.
Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.
Input validation can structurally reject or sanitize data that would otherwise trigger an out-of-bounds write.
Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect and prevent out-of-bounds write defects.
Secure development life cycle mandates practices that prevent out-of-bounds writes.
Application security requirements can specify bounds-checking and safe memory handling.
Secure architecture and engineering principles reduce the likelihood of buffer overflows.
Secure coding directly addresses out-of-bounds writes through language choice and coding standards.
Change management can enforce review gates that catch unsafe memory operations before deployment.