Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
High

Use-After-Free in Samsung KNOX PROCA/FIVE

IdentifiersCVE-2026-20971CWE-416· Use After Free

CVE-2026-20971 is a local kernel use-after-free vulnerability in Samsung KNOX, affecting the PROCA driver and its interaction with the FIVE integrity subsystem prior to Samsung SMR Jan-2026 Release 1. Reported analysis indicates the flaw is caused by a race condition during process integrity state transitions, including execve() and related task state changes, where a task_integrity object can be freed while another kernel path still retains and dereferences a pointer to it. Mentioned vulnerable paths include proc_integrity_value_read(), proc_integrity_label_read(), and a reset-file-related path, yielding practical memory-corruption primitives. Researchers reported that an unprivileged or untrusted local application could trigger kernel memory corruption, and that despite Samsung kernel control-flow integrity mitigations, controlled reallocation of freed memory was still achievable under certain conditions, including manipulation involving loading a non-executable/non-ELF file. Affected devices reportedly span a broad range of Galaxy models, including S9 through S25 and some A-series devices, across Android 13 through 16 on both Exynos and Qualcomm variants.

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 can corrupt kernel memory and may enable local privilege escalation to kernel context, arbitrary code execution, disclosure of kernel memory, and potentially full device compromise. Reported exploitation primitives include memory disclosure that could assist with defeating KASLR, constrained kernel writes, and a function-pointer-related path whose reliability is reduced by Samsung’s kernel CFI/KCFI protections. In practice, the vulnerability is valuable as a post-compromise local escalation primitive from an untrusted app or other initial foothold, and could enable deeper persistence or complete takeover of the affected device.

Mitigation

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

If patching cannot be performed immediately, reduce local attack surface by preventing installation or execution of untrusted applications, disabling sideloading, enforcing application allowlisting through MDM/enterprise mobility controls, restricting developer options where possible, and keeping devices on approved managed builds. Because exploitation is local, enterprise controls that limit user-installed apps and detect compromised devices can materially reduce exposure until the vendor patch is deployed.

Remediation

Patch, then assume compromise.

Apply Samsung Security Maintenance Release Jan-2026 Release 1 or later. Verify affected Galaxy devices are updated to at least the January 2026 Android security patch level containing the fix for CVE-2026-20971 / SVE-2025-2103. Devices no longer receiving Samsung security updates should be retired from sensitive use if they cannot receive the patch.
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 ElectronicsAndroidoperating_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 activity17

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