Cyber Resilience

CVE-2024-28068

Memory Safety in Samsung Exynos 9820 Firmware

Published
09 July 2024
Modified
26 June 2025
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0023 14th percentile
Risk Priority 41 floored blend · peak EPSS

Summary

CVE-2024-28068 is a medium-severity NULL Pointer Dereference (CWE-476) vulnerability in Samsung Exynos 9820 Firmware. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 14th 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 SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A vulnerability was discovered in SS in Samsung Mobile Processor, Wearable Processor, and Modems with versions Exynos 9820, Exynos 9825, Exynos 980, Exynos 990, Exynos 850, Exynos 1080, Exynos 2100, Exynos 2200, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 2400,…

more

Exynos 9110, Exynos W920, Exynos W930, Exynos Modem 5123, and Exynos Modem 5300 that involves a NULL pointer dereference which can cause abnormal termination of a mobile phone via a manipulated packet.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1489 Service Stop Impact
Adversaries may stop or disable services on a system to render those services unavailable to legitimate users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-25073Same product: Samsung Exynos 1080
CVE-2023-37368Same product: Samsung Exynos 1080
CVE-2025-62814Same product: Samsung Exynos 1280
CVE-2025-23100Same product: Samsung Exynos 1280
CVE-2025-62817Same product: Samsung Exynos 1280
CVE-2025-54334Same product: Samsung Exynos 1280
CVE-2025-54326Same product: Samsung Exynos 1280
CVE-2025-62815Same product: Samsung Exynos 1380
CVE-2025-54332Same product: Samsung Exynos 1380
CVE-2024-46922Same product: Samsung Exynos 2400

Affected Assets

samsung
exynos 9820 firmware
all versions
samsung
exynos 9825 firmware
all versions
samsung
exynos 980 firmware
all versions
samsung
exynos 990 firmware
all versions
samsung
exynos 850 firmware
all versions
samsung
exynos 1080 firmware
all versions
samsung
exynos 2100 firmware
all versions
samsung
exynos 2200 firmware
all versions
samsung
exynos 1280 firmware
all versions
samsung
exynos 1380 firmware
all versions
+7 more product configuration(s) — see NVD for full list

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (including static analysis) directly finds null-dereference bugs before deployment.

Documented development standards and tools can enforce null-safety rules and safe pointer usage.

Engineering principles can mandate defensive coding such as explicit null checks before dereference.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices (static analysis, code review, safe coding standards) directly prevent NULL dereference bugs 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.

finds

Security testing can detect NULL dereference defects before release.

prevents

Secure SDLC mandates defensive coding practices that can prevent NULL dereferences.

prevents

Application security requirements can specify input validation and pointer-safety rules.

prevents

Secure architecture principles encourage defensive design that avoids unsafe pointer use.

prevents

Secure coding standards directly require NULL-pointer checks and safe dereference patterns.

References