Samsung Semiconductor Exynos W930 NAS Message length memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00+ |
Summary
A vulnerability was found in Samsung Semiconductor Exynos 850, Exynos 1280, Exynos 1330, Exynos 1380, Exynos 1480, Exynos 1580, Exynos 1680, Exynos 2100, Exynos 2200, Exynos 2400, Exynos 2500, Exynos 5123, Exynos 5300, Exynos 5400, Exynos 5410, Exynos 9110, Exynos W1000, Exynos W920 and Exynos W930 and classified as critical. This impacts an unknown function of the component NAS Message Handler. Such manipulation of the argument length leads to memory corruption. This vulnerability is referenced as CVE-2026-48173. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability was found in Samsung Semiconductor Exynos 850, Exynos 1280, Exynos 1330, Exynos 1380, Exynos 1480, Exynos 1580, Exynos 1680, Exynos 2100, Exynos 2200, Exynos 2400, Exynos 2500, Exynos 5123, Exynos 5300, Exynos 5400, Exynos 5410, Exynos 9110, Exynos W1000, Exynos W920 and Exynos W930 and classified as critical. Affected by this issue is an unknown code of the component NAS Message Handler. The manipulation of the argument length with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. CVE summarizes:
In the NAS message handler, improper validation of the length field in NAS message causes memory corruption
The advisory is available at semiconductor.samsung.com. This vulnerability is handled as CVE-2026-48173 since 05/21/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 11/05/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
- Exynos 850
- Exynos 1280
- Exynos 1330
- Exynos 1380
- Exynos 1480
- Exynos 1580
- Exynos 1680
- Exynos 2100
- Exynos 2200
- Exynos 2400
- Exynos 2500
- Exynos 5123
- Exynos 5300
- Exynos 5400
- Exynos 5410
- Exynos 9110
- Exynos W920
- Exynos W930
- Exynos W1000
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/21/2026 CVE reserved11/05/2026 Advisory disclosed
11/05/2026 VulDB entry created
11/05/2026 VulDB entry last update
Sources
Advisory: semiconductor.samsung.comStatus: Not defined
CNA: samsungsemiconductor
CVE: CVE-2026-48173 (🔒)
GCVE (CVE): GCVE-0-2026-48173
GCVE (VulDB): GCVE-100-431330
Entry
Created: 11/05/2026 04:01Changes: 11/05/2026 04:01 (52)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.