CVE-2025-62817
Plain English Summary
AI-powered analysis for quick understanding
This vulnerability allows an attacker to crash devices using the Exynos 1280 processor, leading to a denial of service, which means users will be unable to use their devices. It occurs when the device tries to process certain data but encounters a programming error, specifically when a required piece of information is missing.
Technical Description
An issue was discovered in Samsung Mobile Processor Exynos 1280, 2200, 1380, 1480, 2400, 1580, and 2500. A NULL pointer dereference of session->ncp_hdr_buf in __pilot_parsing_ncp() causes a denial of service.
CVSS Vector Analysis
Vector String
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploit Resources
Search for proof-of-concept code and exploit modules
Official References
Quick Information
Published
Mar 3, 2026
about 1 month ago
Last Modified
Mar 4, 2026
about 1 month ago
Vendor
samsung
Product
exynos 1280 firmware
Related Vulnerabilities
This vulnerability allows an attacker to cause the affected Samsung mobile processors to crash, leading to a denial of service, which means the device can become unresponsive. To exploit this, the attacker needs to send specially crafted input to the device's boot-up process without proper validation.
This vulnerability allows an attacker to potentially exploit uninitialized memory in the Exynos 2200 processor, which could lead to unauthorized access or manipulation of sensitive data. To take advantage of this flaw, the attacker would need to send specially crafted messages to the device's network services.
This vulnerability allows an attacker to crash devices using the Exynos 1380 processor, leading to a denial of service where the device becomes unresponsive. It occurs when the system tries to manage CPU resources but encounters a programming error, which can happen under certain conditions during operation.
This vulnerability allows an attacker to crash devices using the Samsung Exynos 1280 processor, leading to a denial of service where the device becomes unresponsive. It occurs when the firmware tries to access a part of memory that isn't properly set up, which can happen under certain conditions during firmware loading.