CVE-2025-54329: An issue was discovered in NAS in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 2100, 1280, 2200, 1330, 1380…
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An issue was discovered in NAS in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, 2500, W920, W930, W1000, Modem 5123, Modem 5300, and Modem 5400. The function used to send a multiple-payloads message (including an SMS message) lacks bounds checking, which can lead to a heap overflow.
- Published
- Nov 4, 2025
- Updated
- Nov 5, 2026
- EPSS
- 0.4% · 36th percentile
- CWE
- CWE-122
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| samsung | exynos 1280 firmware | cpe:2.3:o:samsung:exynos_1280_firmware |
| samsung | exynos 1280 | cpe:2.3:h:samsung:exynos_1280 |
| samsung | exynos 1330 firmware | cpe:2.3:o:samsung:exynos_1330_firmware |
| samsung | exynos 1330 | cpe:2.3:h:samsung:exynos_1330 |
| samsung | exynos 1380 firmware | cpe:2.3:o:samsung:exynos_1380_firmware |
| samsung | exynos 1380 | cpe:2.3:h:samsung:exynos_1380 |
| samsung | exynos 1480 firmware | cpe:2.3:o:samsung:exynos_1480_firmware |
| samsung | exynos 1480 | cpe:2.3:h:samsung:exynos_1480 |
| samsung | exynos 1580 firmware | cpe:2.3:o:samsung:exynos_1580_firmware |
| samsung | exynos 1580 | cpe:2.3:h:samsung:exynos_1580 |
| samsung | exynos 2100 firmware | cpe:2.3:o:samsung:exynos_2100_firmware |
| samsung | exynos 2100 | cpe:2.3:h:samsung:exynos_2100 |
and 24 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- samsung exynos 1280 firmwareall versions
- samsung exynos 1330 firmwareall versions
- samsung exynos 1380 firmwareall versions
- samsung exynos 1480 firmwareall versions
- samsung exynos 1580 firmwareall versions
- samsung exynos 2100 firmwareall versions
- samsung exynos 2200 firmwareall versions
- samsung exynos 2400 firmwareall versions
+10 more rows
- samsung exynos 2500 firmwareall versions
- samsung exynos 850 firmwareall versions
- samsung exynos 980 firmwareall versions
- samsung exynos 990 firmwareall versions
- samsung exynos w1000 firmwareall versions
- samsung exynos w920 firmwareall versions
- samsung exynos w930 firmwareall versions
- samsung modem 5123 firmwareall versions
- samsung modem 5300 firmwareall versions
- samsung modem 5400 firmwareall versions
Same product
samsung: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-52910An issue was discovered in the GPU in Samsung Mobile Processor and Wearable Processor Exynos 1280, 2200, 1330, 1380, 1480, 2400.39Monitor
- CVE-2023-28613An issue was discovered in Samsung Exynos Mobile Processor and Baseband Modem Processor for Exynos 1280, Exynos 2200, and Exynos Modem 5300.39Monitor
- CVE-2023-26076An issue was discovered in Samsung Mobile Chipset and Baseband Modem Chipset for Exynos 1280, Exynos 2200, Exynos Modem 5123, Exynos Modem…39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-23095Jun 4, 2025 · An issue was discovered in Samsung Mobile Processor Exynos 1280, 2200, 1380, 1480, 2400.26Monitor
- ← EarlierCVE-2025-23096Jun 4, 2025 · An issue was discovered in Samsung Mobile Processor Exynos 1280, 2200, 1380, 1480, 2400.26Monitor
- Later →CVE-2025-54334Nov 4, 2025 · An issue was discovered in the NPU driver in Samsung Mobile Processor Exynos 1280, 2200, 1380, 1480, 2400, 1580, 2500.30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-23788313 days apartAn issue was discovered in DPU in Samsung Mobile Processor Exynos 1280, 2200, and 1380.16Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-122 · Heap-based Buffer OverflowCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.