CVE-2025-66363
Samsung Exynos 2200 Firmware
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2025-66363 is a high-severity Improper Initialization (CWE-665) vulnerability in Samsung Exynos 2200 Firmware. Its CVSS base score is 7.5 (High).
Operationally, ranked at the 40th 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-8 (Security and Privacy Engineering Principles) — 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-66363 is a vulnerability in the LBS component of the Samsung Mobile Processor Exynos 2200, where there is no check for memory initialization within DL NAS Transport messages. Published on 2026-03-03, this issue falls under CWE-665 (Improper Initialization) and carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
The vulnerability enables remote exploitation over the network with low complexity, requiring no privileges, user interaction, or authentication. Attackers can trigger it to cause high-impact denial of service, such as system crashes or resource exhaustion due to uninitialized memory handling in DL NAS Transport messages.
Samsung provides mitigation details through their product security updates portal at https://semiconductor.samsung.com/support/quality-support/product-security-updates/ and the dedicated CVE page at https://semiconductor.samsung.com/support/quality-support/product-security-updates/cve-2025-66363/. Security practitioners should consult these resources for patch availability and deployment guidance on affected Exynos 2200 devices.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-208236
Vulnerability Data
An issue was discovered in LBS in Samsung Mobile Processor Exynos 2200. There was no check for memory initialization within DL NAS Transport messages.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation directly exercises initialization paths and can reveal missing or incorrect resource setup.
Engineering principles applied during design and implementation can require explicit initialization to a known state.
Requiring the system to fail to a known state structurally reduces the chance that uninitialized resources remain reachable.
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 SDLC practices directly enforce proper resource initialization during coding and testing.
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 can detect uninitialized variables but does not itself enforce initialization practices.
Configuration management can enforce secure defaults and initialization settings but is not the primary control for code-level initialization.
Secure development life cycle mandates initialization checks and secure defaults that directly prevent improper resource initialization.
Secure system architecture and engineering principles require explicit initialization of resources and secure state management.
Secure coding standards explicitly forbid uninitialized variables and mandate proper resource initialization before use.