Samsung Mobile Processor Exynos 1280/1380/1480/2200/2400 load_fw_utc_vector null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Samsung Mobile Processor Exynos 1280/1380/1480/2200/2400. This vulnerability affects the function load_fw_utc_vector. This manipulation causes null pointer dereference.
This vulnerability is handled as CVE-2025-62814. There is not any exploit available.
Details
A vulnerability classified as problematic was found in Samsung Mobile Processor Exynos 1280/1380/1480/2200/2400. Affected by this vulnerability is the function load_fw_utc_vector. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. The summary by CVE is:
An issue was discovered in Samsung Mobile Processor Exynos 1280, 2200, 1380, 1480, and 2400. A NULL pointer dereference of ft_handle in load_fw_utc_vector() causes a denial of service.
It is possible to read the advisory at semiconductor.samsung.com. This vulnerability is known as CVE-2025-62814 since 10/23/2025. Technical details of the vulnerability are known, but there is no available exploit.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.samsung.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.6
VulDB Base Score: 5.7
VulDB Temp Score: 5.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
ADP CISA Base Score: 7.5
ADP CISA Vector: 🔒
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: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
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
10/23/2025 CVE reserved03/03/2026 Advisory disclosed
03/03/2026 VulDB entry created
03/04/2026 VulDB entry last update
Sources
Vendor: samsung.comAdvisory: semiconductor.samsung.com
Status: Confirmed
CVE: CVE-2025-62814 (🔒)
GCVE (CVE): GCVE-0-2025-62814
GCVE (VulDB): GCVE-100-348571
Entry
Created: 03/03/2026 18:34Updated: 03/04/2026 20:39
Changes: 03/03/2026 18:34 (53), 03/04/2026 20:39 (11)
Complete: 🔍
Cache ID: 216:5D6:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.