Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local low-privileged app execution
-
ExploitInvoke AI sound-separation library with crafted input
-
ExecutionTrigger out-of-bounds read/write in lib_sag_ai_sound_sep
-
ImpactCorrupt or disclose adjacent memory for limited local impact
Vulnerability Assessment
| Exploitation Conditions | Exploitation requires local code execution on an affected Samsung mobile device at low privilege (PR:L) - typically a malicious or compromised app - that can reach and supply crafted input to the native AI sound-separation library lib_sag_ai_sound_sep_v2.00.so. There is no remote or network path (AV:L) and no user interaction is needed (UI:N). Limiting factors: the attacker must already hold a local low-privileged foothold, the device must run firmware prior to SMR Oct-2026 Release 1, and the affected library must be present/invokable on the specific Samsung model; impact is bounded to low confidentiality/integrity/availability within the component. |
| Impact | This is a moderate-severity, locally-exploitable memory-safety flaw, not a high-priority remote threat. The vendor-supplied CVSS 4.0 vector (AV:L/AC:L/PR:L/UI:N) and the 4.8 base score are internally consistent with the description's 'local attackers' language - there is no conflict between the metrics and the narrative, which strengthens confidence in the local attack surface. Impact is bounded: VC:L/VI:L/VA:L indicates only low confidentiality, integrity, and availability impact with no scope change (SC:N/SI:N/SA:N), consistent with an out-of-bounds read/write that likely yields limited information disclosure or memory corruption within the context of the component rather than full device compromise. No EPSS score, KEV listing, or POC indicator is present in the supplied data, so there is no public exploitation signal. The practical risk is therefore that of a local privilege/memory issue requiring an already-present low-privileged app or local code execution foothold - a useful link in an exploit chain but not a standalone critical risk. EPSS and exploitation-automatability signals are simply absent here (not low), so they should not be read as evidence of safety; verify against the Samsung advisory and NVD once enrichment is available. |
| Exploit ScenarioDerived | A malicious or compromised low-privileged application already installed on a Samsung mobile device invokes the AI sound-separation library (lib_sag_ai_sound_sep_v2.00.so) with crafted input, triggering an out-of-bounds read and write in the component. The attacker leverages the memory corruption to disclose adjacent memory or corrupt library state, potentially as one stage of a larger local privilege-escalation chain. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Out-of-bounds read and write in the native AI sound-separation library (lib_sag_ai_sound_sep_v2.00.so) on Samsung mobile devices allows a local, low-privileged attacker to read and write memory outside the intended buffer, with impact bounded to low confidentiality, integrity, and availability within the affected component. The flaw is only reachable by an attacker who already holds local code execution on the device - typically a malicious or compromised app capable of supplying crafted input to the library - and affects firmware versions prior to SMR Oct-2026 Release 1. There is no public exploit identified at time of analysis and no indication of confirmed active exploitation; the moderate CVSS 4.8 score reflects the local attack vector and limited per-component impact rather than a remote or high-severity threat.
RemediationAI
Apply the vendor fix by upgrading affected Samsung devices to SMR Oct-2026 Release 1 or later; the exact fixed release and the affected model list are documented in Samsung's security update bulletin at https://security.samsungmobile.com/securityUpdate.smsb?year=2026&month=10 (Vendor-released patch: SMR Oct-2026 Release 1). Where immediate patching is not possible, compensating controls should target the local attack prerequisite - the attacker must already hold low-privileged local code execution and be able to reach the sound-separation library - so restrict installation of untrusted or sideloaded applications, enforce app-store provenance and mobile device management allowlisting, and keep Google Play Protect or equivalent app-scanning enabled; these measures reduce the chance of a hostile app existing on the device but do not remove the underlying memory-safety defect and can be bypassed by a determined attacker who gains a foothold through another vector. Because the flaw is not remotely reachable and requires no user interaction beyond the attacker's own code running locally, network-level controls such as firewalling or segmentation provide no meaningful mitigation, and there is no supported way to disable the shared library from user space without risking loss of AI sound-separation and related audio features. Track the vendor bulletin for the exact firmware version for each model, and note that no public exploit code is identified at time of analysis, so the patching priority remains routine rather than emergency.
Affected VersionsENISA
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 vulnerable component is a vendor-supplied native shared object, lib_sag_ai_sound_sep_v2.00.so, part of Samsung's on-device AI sound-separation processing used by mobile firmware. The defect class is a memory-safety error - reported under the buffer-overflow tag, corresponding to the classic out-of-bounds read/write family (CWE-125/CWE-787 style issues), in which input reaching the library is not adequately bounds-checked before a memory access. Because the code runs as a native library within the mobile platform, an attacker who can already execute code locally at low privilege can invoke or feed the library crafted data and trigger memory accesses outside the allocated region. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L) and the independent CVSS 3.1 assessment (AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L) agree on the fundamentals: local attack vector, low privileges required, no user interaction, and low-level impact confined to the vulnerable component with no scope change. The library is versioned v2.00, and the affected builds are those shipped in firmware prior to the SMR Oct-2026 Release 1 maintenance release; no CWE identifier and no CPE string were supplied in the source data, so product identification rests on the library name and the vendor's SMR advisory.
Know when Android 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
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
Local attack surface and low-privileged app invocation give AV:L/PR:L with AC:L/UI:N; out-of-bounds read/write yields limited C/I/A impact with no scope change.
Primary rating from Vendor (samsung).
CVSS VectorVendor: samsung
DescriptionCVE.org
Out-of-bounds read and write in lib_sag_ai_sound_sep_v2.00.so prior to SMR Oct-2026 Release 1 allows local attackers to read and write out-of-bounds memory.
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.
Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466
Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A
Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp
Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef
Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK
An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows
luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.
The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01
EUVD-2026-97183
GHSA-pjpr-mc9x-58v2
NVD
CVE.org
EPSS
Exploit-DB