CVE-2025-54333
Samsung Exynos 1380 Firmware ≤ 2025-07
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LSummary
CVE-2025-54333 is a medium-severity Release of Invalid Pointer or Reference (CWE-763) vulnerability in Samsung Exynos 1380 Firmware. Its CVSS base score is 5.3 (Medium).
Operationally, ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-16 (Memory Protection) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-37847
Vulnerability Data
An issue was discovered in NPU in Samsung Mobile Processor Exynos 1380 through July 2025. There is an Invalid Pointer Dereference of node in the get_vs4l_profiler_node function.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly enforces memory-protection mechanisms that block invalid pointer dereferences such as the one in get_vs4l_profiler_node.
Requires timely patching of the identified flaw in the Exynos NPU driver before exploitation can occur.
Process isolation limits the blast radius of a dereference occurring inside the NPU subsystem.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent invalid pointer release errors during development.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect invalid pointer releases before release.
Secure SDLC practices can mandate proper memory-management APIs and reviews that catch incorrect deallocation.
Application security requirements can specify correct use of release functions and pointer validation.
Secure architecture principles include safe memory handling and resource-lifetime rules.
Secure coding standards directly prohibit mismatched or incorrect pointer-release calls.