Samsung Android
CVE-2025-21052
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall or compromise local app (PR:L)
-
DeliveryDeliver crafted JPEG to decoder
-
ExploitTrigger out-of-bounds write in libpadm.so
-
ExecutionCorrupt memory / hijack control flow
-
ImpactEscalate privileges or 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 | Requires local access with at least low privileges (PR:L) - in practice a malicious or compromised app running on the Samsung Android 13 device that can route a crafted JPEG into a component backed by libpadm.so. The out-of-bounds write only occurs under a 'specific condition' during JPEG pre-processing (the exact malformed-image trigger is not detailed in the available data), so not every JPEG will fire the bug. Limiting factors: no remote/network vector (AV:L), the attacker must already be able to run code or deliver input locally, and devices patched at SMR Oct-2025 Release 1 or later are not affected. No user interaction is required (UI:N) once the malicious input is delivered. |
| Impact | This is a genuine but second-tier priority: a high-CVSS (7.8) local privilege-escalation/memory-corruption flaw whose real-world risk signals point to opportunistic rather than widespread exploitation. The CVSS vector (AV:L/AC:L/PR:L/UI:N) confirms a LOCAL attack vector requiring some pre-existing privilege (PR:L) - not remote, despite JPEG decoding sometimes being reachable over the network; the input data does not show a remote delivery path, so network exploitation is not substantiated. EPSS is very low (0.13%, 2nd percentile) and there is no CISA KEV listing and no referenced public exploit, so there is no evidence of active exploitation or weaponized POC. The high triad impact (C:H/I:H/A:H, scope unchanged) reflects potential code execution within the context that invokes libpadm.so. These signals are internally consistent: a serious memory-corruption bug that in practice requires a local malicious app or local access, making it a chaining component for jailbreak/privesc rather than a mass-exploitation threat. Note the 'specific condition' qualifier in the description means not all JPEG inputs trigger the bug - the exact trigger condition is not disclosed in the provided data and should be verified against Samsung's SMR Oct-2025 bulletin. |
| Exploit ScenarioDerived | A malicious or compromised app installed on a Samsung Android 13 device supplies a specially crafted JPEG to a system component that uses libpadm.so for decoding, triggering an out-of-bounds write during pre-processing. The resulting memory corruption can be shaped to corrupt adjacent data or control flow, enabling code execution or privilege escalation in the decoding process's context. No public exploit identified at time of analysis; exploitation requires local code execution with at least low privileges (PR:L). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
An out-of-bounds write in the libpadm.so library on Samsung Android 13.0 devices allows an attacker with local code execution to corrupt memory during JPEG pre-processing, which can lead to privilege escalation or code execution in the context of the affected process. The flaw is triggered only under a specific, vendor-unspecified condition when a crafted JPEG reaches a component backed by libpadm.so; the CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N) confirms it requires local access with low privileges and no user interaction. There is no confirmed active exploitation and no public exploit identified at time of analysis, and the low EPSS score of 0.13% (2nd percentile) indicates opportunistic rather than widespread risk; Samsung addressed it in SMR Oct-2025 Release 1.
RemediationAI
Apply the Samsung SMR Oct-2025 Release 1 (or later) firmware update for the affected Galaxy model, which contains the vendor fix for the libpadm.so out-of-bounds write; the update is delivered through the standard over-the-air security maintenance release channel, and the advisory is at https://security.samsungmobile.com/securityUpdate.smsb?year=2025&month=10. Until the device is patched, the most effective compensating controls are to reduce the attack surface that can deliver a crafted JPEG to a libpadm-backed component: restrict sideloading and untrusted app installation (blocks the local vector, at the cost of user flexibility), tighten app permissions and remove or disable untrusted applications that handle images, and avoid opening image files from unverified sources on the affected device. Enterprise administrators can enforce a minimum firmware/SMR compliance policy on managed Samsung Android 13.0 devices to force the October 2025 patch level; the trade-off is that non-compliant devices must be quarantined from corporate resources, which can disrupt users who delay updating. No vendor-released patch was identified as bypassable - the fix is the SMR update itself - and there is no public exploit code to prioritize emergency workarounds beyond prompt patching.
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
libpadm.so is a Samsung userspace shared library involved in image decoding and pre-processing on Galaxy devices; the vulnerable routine mishandles malformed JPEG input before decoding, producing a heap out-of-bounds write classified as CWE-787 (Out-of-bounds Write). Because the bug lives in a userspace library, the immediate impact is memory corruption of the process that parses the image, which can be leveraged to hijack execution flow in that process's security context. The CPE data maps the issue to Samsung's Android 13.0 firmware across multiple SMR levels (ranging from SMR Dec-2021 R1 through SMR Aug-2025 R1), confirming that the defect persisted through many maintenance releases until it was fixed. The CVSS vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H indicates a low-complexity, low-privilege, local attack path with high confidentiality, integrity, and availability impact, scoped to the vulnerable component rather than crossing a security boundary on its own.
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
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local delivery of a crafted image by a low-privileged app (AV:L/PR:L), no user interaction needed, out-of-bounds write yields full code-execution-level impact with unchanged scope.
Primary rating from NVD.
CVSS VectorNVD
DescriptionNVD
Out-of-bounds write under specific condition in the pre-processing of JPEG decoding in libpadm.so prior to SMR Oct-2025 Release 1 allows local attackers to cause memory corruption.
Executive ViewAI
A high-severity out-of-bounds write in Samsung Android 13.0's libpadm.so library allows a local attacker with low privileges to corrupt memory and potentially escalate code execution on affected devices. This matters because Samsung Android 13.0 devices are likely part of the managed mobile fleet, and while no public exploit identified at time of analysis, a local foothold could be leveraged to access corporate data or services. Vendor-released patch: SMR Oct-2025 Release 1, so leadership should ensure fleet-wide patching and verify compliance.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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
Remote, unauthenticated attackers can write files of their choosing with system-level authority on Samsung MagicINFO 9 S
Samsung MagicINFO 9 Server contains a path traversal vulnerability allowing unauthenticated attackers to write arbitrary
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
Web Viewer 1.0.0.193 on Samsung SRN-1670D devices suffers from an Unrestricted file upload vulnerability: 'network_ssl_u
Web Viewer 1.0.0.193 on Samsung SRN-1670D devices allows remote attackers to read arbitrary files via a request to an un
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
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
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
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
Samsung Internet Browser 5.4.02.3 allows remote attackers to bypass the Same Origin Policy and obtain sensitive informat
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
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
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB