CVE-2025-23107

| EUVD-2025-16769 HIGH
2025-06-03 [email protected]
8.6
CVSS 3.1
Share

CVSS Vector

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

3
EUVD ID Assigned
Mar 14, 2026 - 17:04 euvd
EUVD-2025-16769
Analysis Generated
Mar 14, 2026 - 17:04 vuln.today
CVE Published
Jun 03, 2025 - 17:15 nvd
HIGH 8.6

Description

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

Analysis

Critical out-of-bounds write vulnerability in Samsung's Exynos 1480 and 2400 mobile processors caused by insufficient length validation. This vulnerability affects Samsung Galaxy devices and other OEM devices utilizing these SoCs, allowing remote, unauthenticated attackers to execute code with high integrity impact and potential system compromise. The high CVSS score of 8.6 reflects the network-exploitable nature and lack of authentication requirements, though real-world exploitation depends on the specific attack surface exposed in affected device implementations.

Technical Context

The vulnerability resides in Samsung's Exynos mobile processor line (specifically the 1480 and 2400 models), which serve as the primary system-on-chip (SoC) for Samsung Galaxy flagship devices and are licensed to other OEMs. The root cause is classified as CWE-787 (Out-of-bounds Write), which occurs when code writes data beyond the boundaries of an allocated memory buffer without proper length validation. This typically manifests in processor firmware, bootloader, or secure enclave components that parse untrusted input without bounds checking. The lack of a length check suggests the vulnerability exists in a parsing routine—possibly in modem firmware processing, secure element communication, or inter-processor communication (IPC) mechanisms—where an attacker can supply malformed packets or messages that exceed expected buffer sizes, corrupting adjacent memory regions.

Affected Products

Samsung Exynos 1480 processor (found in Galaxy S24 FE and mid-range Galaxy devices). Samsung Exynos 2400 processor (found in Galaxy S24, S24+, S24 Ultra, and other 2024+ flagship devices). Third-party OEM devices using Exynos 1480 or 2400 SoCs, including devices from carriers and regional manufacturers. CPE identifiers would typically follow the pattern: cpe:2.3:h:samsung:exynos_1480:*:*:*:*:*:*:*:* and cpe:2.3:h:samsung:exynos_2400:*:*:*:*:*:*:*:*. Affected firmware versions are those shipped prior to Samsung's security patch release; specific patch versions are not provided in available intelligence but would typically be delivered via monthly security updates or emergency out-of-band patches given the severity.

Remediation

Users with affected devices (Galaxy S24 series, S24 FE, and related models) should immediately apply the latest available firmware/security updates through Settings > System > System Update > Check for Updates or via Samsung's SmartSwitch software. OEMs using Exynos 1480/2400 should contact Samsung for emergency firmware patches. Samsung will release fixes through monthly security updates (likely available in January 2025 or sooner depending on discovery/disclosure timeline). Users unable to patch immediately should: (1) disable unnecessary network-exposed services and features, (2) avoid connecting to untrusted networks, (3) use VPN or network segmentation where possible, and (4) monitor Samsung's Security Advisory and Mobile Security Release Notes for specific CVE guidance. No known workarounds exist for this processor-level vulnerability; patching is the only mitigation. Vendor advisories and detailed patch notes should be monitored at security.samsungmobile.com and Samsung's official security bulletin pages.

Priority Score

43
Low Medium High Critical
KEV: 0
EPSS: +0.1
CVSS: +43
POC: 0

Share

CVE-2025-23107 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy