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 vulnerability in Samsung’s KNOX framework, specifically affecting the PROCA driver and its interaction with the FIVE integrity subsystem prior to SMR Jan-2026 Release 1. The flaw is a race-condition-driven use-after-free involving the task_integrity object used to track process integrity state. During process state transitions such as execve() (and reportedly fork-related paths), one kernel path can free an existing task_integrity object while another path continues to dereference the stale pointer, creating a dangling reference in kernel memory. Reported vulnerable paths include procfs-backed integrity read handlers such as proc_integrity_value_read() and proc_integrity_label_read(). Researchers reported that an unprivileged application could trigger the race and reclaim the freed memory with controlled data, including via a technique involving loading a non-executable/non-ELF file, resulting in practical kernel memory corruption despite Samsung kernel control-flow integrity mitigations. Samsung patched the issue in its January 2026 security update.

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 arbitrary code execution in kernel context. Reported exploitation primitives include kernel memory disclosure, constrained kernel write/corruption, and other memory-corruption capabilities that can be used for local privilege escalation and potentially full device compromise. Because the flaw is in a privileged Knox kernel component, exploitation can give an attacker deeper control over the device and make the vulnerability useful in post-compromise exploit chains, including on enterprise-managed phones.

Mitigation

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

If immediate patching is not possible, reduce opportunities for local code execution by preventing installation of untrusted applications, disabling sideloading, enforcing application allowlisting, and using MDM/enterprise mobility controls to keep devices on approved builds. Limit physical access to devices, monitor for signs of malicious app installation or post-compromise activity, and prioritize replacement or isolation of devices that are no longer receiving Samsung security updates.

Remediation

Patch, then assume compromise.

Update affected Samsung devices to SMR Jan-2026 Release 1 or later, as Samsung states the issue is fixed in the January 2026 security update. Verify the device is running a January 2026 or newer Android/Samsung security patch level. For fleet environments, enforce patch compliance across affected Galaxy devices, including S9 through S25 generations and affected A-series models on Android 13 through 16.
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 activity18

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