CVE-2025-62816
Denial of Service via Unvalidated Input in Samsung Exynos Processors
Publication date: 2026-03-03
Last updated on: 2026-03-04
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| samsung | exynos_1280_firmware | * |
| samsung | exynos_1380_firmware | * |
| samsung | exynos_1480_firmware | * |
| samsung | exynos_1580_firmware | * |
| samsung | exynos_2200_firmware | * |
| samsung | exynos_2400_firmware | * |
| samsung | exynos_2500_firmware | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-20 | The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-62816 is a medium-severity vulnerability found in the Neural Processing Unit (NPU) component of Samsung Exynos processors, including models 1280, 1380, 1480, 1580, 2200, 2400, and 2500.
The vulnerability occurs because the input to the VS4L_VERTEXIOC_BOOTUP interface is not properly validated, which can cause the system to experience a denial of service (DoS) condition.
How can this vulnerability impact me? :
This vulnerability can impact you by causing a denial of service (DoS) on devices using the affected Samsung Exynos processors. This means that the device or the Neural Processing Unit may become unresponsive or crash when exposed to malicious or malformed input targeting the VS4L_VERTEXIOC_BOOTUP interface.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
There are no specific detection methods or commands provided to identify this vulnerability on your network or system.
What immediate steps should I take to mitigate this vulnerability?
No specific mitigation steps or patched versions are provided for this vulnerability at this time.