Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Critical

Samsung Exynos NPU Driver Out-of-Bounds Write Privilege Escalation

IdentifiersCVE-2025-23099CWE-787· Out-of-bounds Write

CVE-2025-23099 is a high-severity out-of-bounds write vulnerability in the Samsung Exynos NPU driver affecting Exynos 1480 and Exynos 2400 platforms, including Samsung Galaxy S24+ devices running Android 14. The root cause is a missing length check in NPU queue management. Specifically, the vulnerable logic is in the npu_queue_prepare and npu_queue_alloc functions: npu_queue_prepare allocates input and output queues via npu_queue_alloc and sets NPU_QUEUE_STATE_ALLOC, while npu_queue_alloc returns early without reallocating if that state is already set. As a result, a subsequent call to npu_queue_prepare with larger attacker-controlled container counts can reuse an earlier, smaller allocation. Execution then proceeds into npu_queue_mapping while trusting the larger user-supplied counts, leading to corruption of queue_list->count and q_container->count and ultimately an out-of-bounds write in kernel memory.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a local attacker to corrupt kernel memory from a low-privilege context, resulting in local privilege escalation. Samsung assigned CVSS v3.1 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), indicating potential high impact to confidentiality, integrity, and availability. Depending on exploitation reliability, the flaw can enable elevation from an untrusted application context to higher privileges through kernel-level memory corruption.

Mitigation

If you can’t patch tonight, do this now.

Until patched firmware is installed, exposure can be reduced by limiting installation and execution of untrusted third-party applications, especially on affected Samsung devices where local app access is possible. Enterprise controls such as application allowlisting, MDM-enforced app restrictions, and rapid deployment of Samsung security updates can reduce risk. Because the issue is locally exploitable from the untrusted_app SELinux context and requires no user interaction, there is no complete mitigation short of applying the vendor patch.

Remediation

Patch, then assume compromise.

Samsung released a patch for CVE-2025-23099 in its Product Security Update on 2025-06-02. Remediation is to apply Samsung's security update on affected devices and ensure firmware incorporating the vendor fix is deployed on Exynos 1480 and 2400-based products. The underlying fix should enforce proper length validation and ensure queue allocations are resized or rejected when subsequent preparation requests specify larger container counts than previously allocated.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Samsung ElectronicsExynos 1480 Firmwareoperating_system
Samsung ElectronicsExynos 2400 Firmwareoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.