What is the CVSS score of CVE-2025-23103?

CVE-2025-23103 has a CVSS 3.1 base score of 8.6 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L. EPSS exploitation probability: 0.1%.

Which versions of Exynos 1480 Firmware are affected by CVE-2025-23103?

A memory corruption vulnerability affects Samsung's Exynos 1480 and 2400 mobile processors, potentially allowing attackers to execute arbitrary code on affected devices.

How to fix or mitigate CVE-2025-23103?

Within 24 hours: Identify all deployed Samsung devices using Exynos 1480/2400 processors and restrict their access to sensitive corporate systems; document affected device inventory. Within 7 days: Contact Samsung for patch timeline estimates and evaluate temporary network segmentation or Mobile Device Management (MDM) restrictions; communicate risk to device users. Within 30 days: Develop a patch deployment plan upon Samsung's release; prioritize devices with high-risk data access; establish a rollback procedure and test patches in a controlled environment before enterprise deployment.

Exynos 1480 Firmware CVE-2025-23103

EUVD-2025-16752 HIGH

Out-of-bounds Write (CWE-787)

2025-06-03 cve@mitre.org

Buffer Overflow Samsung Exynos 1480 Firmware Exynos 2400 Firmware

8.6

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.6 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

Low

Lifecycle Timeline

EUVD ID Assigned

Mar 14, 2026 - 17:04 euvd

EUVD-2025-16752

Analysis Generated

Mar 14, 2026 - 17:04 vuln.today

CVE Published

Jun 03, 2025 - 16:15 nvd

HIGH 8.6

DescriptionCVE.org

An issue was discovered in Samsung Mobile Processor Exynos 1480 and 2400. The lack of a length check leads to out-of-bounds writes.

AnalysisAI

CVE-2025-23103 is an out-of-bounds write vulnerability in Samsung's Exynos 1480 and 2400 mobile processors caused by insufficient length validation, allowing remote unauthenticated attackers to achieve high confidentiality impact with medium integrity and availability impact. The vulnerability has a CVSS score of 8.6 with low attack complexity and no privilege requirements, making it a significant risk to Samsung Galaxy devices using these processors; exploitation status and active use in the wild have not been confirmed at this time.

Technical ContextAI

The vulnerability exists in Samsung Mobile Processor Exynos 1480 and 2400 SoCs (System-on-Chip), which are primary processors used in Samsung Galaxy flagship and mid-range devices. The root cause is classified as CWE-787 (Out-of-bounds Write), indicating that code processing network input or other external data fails to validate buffer length before writing, allowing attackers to overflow heap or stack memory. The Exynos processors handle low-level hardware operations, cryptographic functions, and secure enclave processing; a flaw at this level can compromise the entire device security model. The lack of length checking suggests the vulnerability exists in firmware or bootloader code responsible for parsing or processing protocol messages, likely in network stack handling or secure communication channels.

RemediationAI

Samsung must release firmware/bootloader patches addressing the length validation flaw in affected Exynos processors. Users should: (1) Apply all available Samsung security updates immediately upon release, prioritizing devices with Exynos 1480/2400; (2) Monitor Samsung Security Advisory pages for firmware patches specific to CVE-2025-23103; (3) Avoid untrusted networks and disable unnecessary network services pending patches; (4) Enable all available security features (Knox, SELinux enforcement); (5) Consider network segmentation for critical Samsung devices. Vendor mitigation may include disabling vulnerable firmware code paths if identified. Samsung should release coordinated security advisories with clear device model mapping and patch timeline. Patch availability dates and version numbers should be published immediately to samsung.com/security.