Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local low-priv execution on Exynos 1580 device
-
DeliveryAccess custos_iwc device node
-
ExploitSubmit oversized shared memory allocation request
-
ExecutionDriver omits bounds validation
-
PersistOOB read/write crosses TrustZone boundary
-
ImpactLeak secure-world data or corrupt CustOS memory
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 code execution on a Samsung Exynos 1580 device with at least low-level user privileges (PR:L) sufficient to open and interact with the custos_iwc device node - in practice, a shell session or native app granted access by the device's SELinux policy. The attacker must submit a specifically crafted oversized shared memory request that bypasses any initial size checks, contributing to the high attack complexity (AC:H) rating. Limiting factors: (1) the attack vector is strictly local - no remote or network-based exploitation path is described or implied; (2) the custos_iwc device node is likely restricted by Samsung's SELinux policy to designated system or HAL processes, meaning arbitrary low-privileged apps may not directly reach the vulnerable interface; (3) the Exynos 1580 is affected, not other Exynos variants; (4) the scope change (S:C) indicates TEE boundary crossing but not necessarily full secure-world compromise. |
| Impact | The official CVSS 3.1 score of 4.2 (Medium) is internally consistent with its vector (AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:L) and appropriately reflects local-only reachability, high attack complexity, and constrained impact. However, the I:N metric is questionable given CWE-787 (Out-of-bounds Write) is the designated weakness - OOB writes can corrupt adjacent memory, which should normally attract at least I:L; the official rating appears to understate integrity impact. No EPSS score was provided in source data, no CISA KEV listing exists, and no public proof-of-concept has been identified, all consistent with the low practical exploitation likelihood suggested by the 4.2 score. Real-world risk is further bounded by: (1) mandatory local code execution on an Exynos 1580 device, (2) the custos_iwc device node being likely restricted via SELinux policy to Samsung system processes, reducing the set of exploitable privilege contexts, and (3) AC:H indicating the exploit requires precise crafting or timing. This vulnerability is realistically relevant as a component in a multi-stage local privilege escalation or TEE bypass chain rather than a standalone critical risk. |
| Exploit ScenarioDerived | A local attacker with low-privileged shell access on a Samsung Galaxy A55 (Exynos 1580) opens the custos_iwc device node and issues a crafted ioctl or mmap call with a deliberately oversized shared memory length. The CustOS driver services the request without bounding the size, and the attacker reads memory beyond the allocated region - potentially extracting secure-world key material or session tokens - or writes past the buffer to corrupt adjacent CustOS runtime structures. No public proof-of-concept exploit has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 14, 2026
Out-of-bounds memory access in Samsung's CustOS Driver on Exynos 1580 processors exposes a local low-privileged attacker to cross-TEE-boundary memory read and write primitives. The fault is triggered by submitting an oversized shared memory allocation request to the custos_iwc inter-world communication device, which the driver services without adequate bounds validation, potentially leaking secure-world data or corrupting CustOS runtime state. No public exploit code has been identified and CISA has not listed this in KEV at time of analysis.
RemediationAI
Apply the Samsung security update addressing CVE-2026-33957 via the standard Galaxy OTA update mechanism for affected Exynos 1580 devices. The vendor advisory at https://semiconductor.samsung.com/support/quality-support/product-security-updates/cve-2026-33957/ should be consulted for the exact patched firmware version, which was not independently extractable from the available data. As a compensating control prior to patching, system administrators managing enterprise Android fleets via MDM can restrict sideloaded or third-party application access to the custos_iwc device node by enforcing SELinux policy tightening or limiting device-node permissions - note that this may disrupt legitimate Samsung CustOS-dependent platform services such as secure key storage or DRM operations. No network-level workarounds apply given the local-only attack vector.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CustOS is Samsung's Trusted Execution Environment (TEE) implementation for Exynos SoCs, leveraging ARM TrustZone to isolate secure-world workloads from the normal Android environment. The custos_iwc device node exposes an inter-world communication (IWC) interface that allows normal-world callers - typically Samsung HAL components - to request shared memory regions for cross-world data exchange. CWE-787 (Out-of-bounds Write) is the listed root cause, and the description confirms a co-occurring out-of-bounds read: when the caller specifies an oversized shared memory length, the driver fails to clamp or reject the request against the actual buffer bounds, producing accesses that extend past the allocated region in both directions. The Scope:Changed metric (S:C) in the CVSS vector reflects the TrustZone trust-boundary crossing inherent to IWC operations - a miscalculated allocation can reach into or corrupt secure-world memory regions. The CPE cpe:2.3:a:samsung:exynos_1580_firmware:*:*:*:*:*:*:*:* covers all Exynos 1580 firmware revisions prior to the vendor patch.
Know when Exynos 1580 Firmware 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:H/PR:L/UI:N/S:C/C:L/I:N/A:L
OOB write (CWE-787) warrants I:L; official I:N understates memory corruption potential across the TEE boundary.
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
DescriptionCVE.org
An issue was discovered in CustOS Driver in Samsung Mobile Processor Exynos 1580. Requesting oversized shared memory from the custos_iwc device enables out-of-bounds read and write, potentially leading to memory corruption or information leakage.
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.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Exynos 1580 Firmware
View allIn RRC in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 13
Samsung Exynos processors (multiple models including 980, 990, 2100, 2200, 2400) and modems have an out-of-bounds write
An issue was discovered in Samsung Mobile Processor Exynos 1380, 1480, 2400, and 1580. Incorrect Handling of the NL80211
An issue was discovered in the WiFi driver in Samsung Mobile Processor Exynos 1380, 1480, 2400, 1580. Mishandling of an
An issue was discovered in Samsung Mobile Processor Exynos 1280, 2200, 1380, 1480, 2400, 1580, and 2500. A NULL pointer
An issue was discovered in L2 in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 240
Denial of service in Samsung Exynos USIM firmware across mobile, wearable, and modem processors allows unauthenticated r
System crash in Samsung Exynos processors (980/990/850/1080/2100/1280/2200/1330/1380/1480/2400/1580/2500/9110, Wearable
An issue was discovered in the Camera in Samsung Mobile Processor and Wearable Processor Exynos 1330, 1380, 1480, 2400,
An issue was discovered in the GPU driver in Samsung Mobile Processor Exynos 1480, 2400, 1580, 2500. Rated medium severi
Exynos 980 Firmware versions up to - is affected by allocation of resources without limits or throttling (CVSS 6.2).
Exynos 980 Firmware versions up to - is affected by allocation of resources without limits or throttling (CVSS 6.2).
EUVD-2026-77160
GHSA-4cjw-7m6g-3q48
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB