Skip to main content

Samsung Android CVE-2025-21053

HIGH
Out-of-bounds Write (CWE-787)
2025-10-10 mobile.security@samsung.com
7.8
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Install or compromise local app (PR:L)
  2. Delivery
    Deliver crafted JPEG to libpadm.so decoder
  3. Exploit
    Trigger out-of-bounds write in header parsing
  4. Execution
    Corrupt process memory
  5. Impact
    Escalate privileges / execute code

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires local access on an affected Samsung Android 13 device - specifically the ability to run code or an app (PR:L) that can supply attacker-controlled image data to the JPEG decoding path in libpadm.so, whose header parser contains the out-of-bounds write. The flaw is reached by processing a crafted JPEG header, so the limiting factors are: the attacker must already be present on the device (no remote/network vector, AV:L), must hold at least low privileges, and the device must be running a Samsung Android 13 build at a security maintenance release prior to SMR Oct-2025 Release 1 (patched builds are not affected). No user interaction is required (UI:N).

Impact

Signals are consistent and point to a genuine but locally-scoped risk. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 HIGH) describes a locally-exploitable, low-complexity, low-privilege flaw with high impact to confidentiality, integrity, and availability - the classic profile of an out-of-bounds write (CWE-787) reached by a malicious or compromised local app. Exploitation signals are notably weak: EPSS is only 0.13% (2nd percentile), the CVE is NOT in CISA KEV, and no public POC is indicated, so there is no public exploit identified at time of analysis and no evidence of active exploitation. SSVC framing would place this as Exploitation=none, Automatable=no (local vector requires code already running on-device), Technical Impact=total. The combination of a local-only vector with no public exploit and very low EPSS means this is a meaningful patch-worthy defect for Samsung device fleets but NOT an emergency internet-facing threat - it is a credible privilege-escalation/memory-corruption primitive rather than a widely-exploited one. All signals align here; there is no conflict between CVSS and the description, both of which agree on local access (AV:L matches 'allows local attackers').

Exploit ScenarioDerived

A low-privileged malicious or compromised Android application installed on an affected Samsung device feeds a specially crafted JPEG with a malformed header to the vulnerable libpadm.so decoder. Parsing the crafted header triggers an out-of-bounds write that corrupts memory, which a skilled attacker can shape toward code execution or privilege escalation in the context of the image-handling process. No public exploit code is identified at time of analysis, and the local attack vector requires the attacker to already have code execution on the device.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 08, 2026

An out-of-bounds write in the JPEG header parser of libpadm.so on Samsung Android 13 devices allows a locally present attacker to corrupt memory by supplying a crafted JPEG image to the decoding path. Exploitation requires the attacker to already have code or an app running on the device with at least low privileges (CVSS:3.1/AV:L/AC:L/PR:L/UI:N), and no user interaction is needed, so the flaw is locally scoped rather than remotely reachable. Only builds at a security maintenance release before SMR Oct-2025 Release 1 are affected; there is no public exploit identified at time of analysis and the EPSS score is low (0.13%, 2nd percentile), so near-term exploitation risk is limited.

RemediationAI

Apply the vendor fix by upgrading affected Samsung Android 13 devices to SMR Oct-2025 Release 1 or later firmware; this is the only remediation that corrects the out-of-bounds write in libpadm.so, as detailed in the Samsung Security Maintenance Release bulletin at https://security.samsungmobile.com/securityUpdate.smsb?year=2025&month=10 (patch availability per vendor advisory). Samsung distributes these fixes over-the-air, so users and managed fleets should verify the device's build number reflects the October 2025 SMR or newer and enforce patching through MDM/EMM policy. Until a device can be updated, compensating controls are constrained because the defect is inside the platform image: reducing local attacker presence by restricting sideloading, disabling developer options and untrusted app installs, and tightening app permissions lowers the chance an attacker can trigger the JPEG parsing path, though these measures do not remove the underlying memory corruption. Because exploitation needs a local foothold, keeping Play Protect and app vetting active and removing unnecessary apps reduces the attack surface; there is no network-facing configuration change that mitigates this flaw, and no vendor workaround beyond upgrading firmware is identified.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is a classic out-of-bounds write (CWE-787) in the JPEG header parsing logic of libpadm.so, a Samsung platform library bundled with the Android firmware. When attacker-controlled JPEG data is fed into the decoder, insufficient bounds validation of header fields - such as dimensions, segment lengths, or table offsets - lets writes occur past the end of an allocated buffer, producing heap or buffer memory corruption. Because the affected library is part of the device platform rather than an app, the corruption occurs in the context of the process that performs JPEG decoding, and the CVSS vector (AV:L, PR:L, S:U) confirms the path is reachable only by an attacker already executing locally on the device, with high confidentiality and integrity impact but no availability impact. The Samsung CPE data ties the exposure to Samsung's Android 13.0 firmware under a wide range of security maintenance releases, indicating the fix is delivered as part of the monthly SMR regime rather than as an application update.

Know when Samsung gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Local-only reachable via on-device app (AV:L, PR:L), low-complexity deterministic parser bug (AC:L), no interaction (UI:N), and an out-of-bounds write yielding full C/I/A impact within the unchanged scope.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionNVD

Out-of-bounds write in the parsing header for JPEG decoding in libpadm.so prior to SMR Oct-2025 Release 1 allows local attackers to cause memory corruption.

Executive ViewAI

Why It Matters

Samsung Android 13 devices running libpadm.so before SMR Oct-2025 Release 1 are exposed to a high-severity local memory corruption flaw in JPEG parsing. A malicious app already running with low privileges could exploit this to corrupt memory, potentially compromising data or device integrity for managed mobile users. Leadership should care because targeted local attacks could bypass perimeter defenses, though no public exploit identified at time of analysis and near-term exploitation risk is limited.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include restricting installation of untrusted apps, enforcing mobile device management and app allowlisting to limit low-privilege local code execution, avoiding processing of untrusted JPEG files on affected devices where possible, and upgrading to SMR Oct-2025 Release 1 or later when available.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
High
Samsung is a top global Android OEM; huge installed base of Android 13 devices
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
Medium

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Affected Products (CPE)NVD

cpe:2.3:o:samsung:android:13.0:-:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-apr-2022-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-apr-2023-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-apr-2024-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-apr-2025-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-aug-2022-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-aug-2023-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-aug-2024-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-aug-2025-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-dec-2021-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-dec-2022-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-dec-2023-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-dec-2024-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-feb-2022-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-feb-2023-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-feb-2024-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-feb-2025-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-jan-2022-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-jan-2023-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:13.0:smr-jan-2024-r1:*:*:*:*:*:*
+ 87 more
CVE-2024-7399 CRITICAL POC
9.8 Aug 12

Remote, unauthenticated attackers can write files of their choosing with system-level authority on Samsung MagicINFO 9 S

CVE-2025-4632 CRITICAL POC
9.8 May 13

Samsung MagicINFO 9 Server contains a path traversal vulnerability allowing unauthenticated attackers to write arbitrary

CVE-2012-4333 CRITICAL POC
10.0 Aug 14

Multiple stack-based buffer overflows in the BackupToAvi method in the (1) UMS_Ctrl 1.5.1.1 and (2) UMS_Ctrl_STW 2.0.1.0

CVE-2017-16524 HIGH POC
8.8 Nov 06

Web Viewer 1.0.0.193 on Samsung SRN-1670D devices suffers from an Unrestricted file upload vulnerability: 'network_ssl_u

CVE-2015-8279 HIGH POC
8.6 Jan 15

Web Viewer 1.0.0.193 on Samsung SRN-1670D devices allows remote attackers to read arbitrary files via a request to an un

CVE-2016-0998 HIGH POC
8.8 Mar 12

Use-after-free vulnerability in Adobe Flash Player before 18.0.0.333 and 19.x through 21.x before 21.0.0.182 on Windows

CVE-2016-0999 HIGH POC
8.8 Mar 12

Use-after-free vulnerability in Adobe Flash Player before 18.0.0.333 and 19.x through 21.x before 21.0.0.182 on Windows

CVE-2016-0997 HIGH POC
8.8 Mar 12

Use-after-free vulnerability in Adobe Flash Player before 18.0.0.333 and 19.x through 21.x before 21.0.0.182 on Windows

CVE-2016-1000 HIGH POC
8.8 Mar 12

Use-after-free vulnerability in Adobe Flash Player before 18.0.0.333 and 19.x through 21.x before 21.0.0.182 on Windows

CVE-2017-17692 HIGH POC
7.5 Dec 21

Samsung Internet Browser 5.4.02.3 allows remote attackers to bypass the Same Origin Policy and obtain sensitive informat

CVE-2016-1002 HIGH POC
8.8 Mar 12

Adobe Flash Player before 18.0.0.333 and 19.x through 21.x before 21.0.0.182 on Windows and OS X and before 11.2.202.577

CVE-2016-1010 HIGH
8.8 Mar 12

Integer overflow in Adobe Flash Player before 18.0.0.333 and 19.x through 21.x before 21.0.0.182 on Windows and OS X and

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