Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
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's KNOX security framework, specifically in the PROCA driver and its interaction with the FIVE integrity subsystem, affecting devices prior to SMR Jan-2026 Release 1. Reporting indicates the flaw is caused by a race condition during process integrity state transitions such as fork or execve(), where a task_integrity object can be freed while another code path continues to reference it. In the described vulnerable flow, the old integrity object is released during replacement, after which procfs-backed read paths such as proc_integrity_value_read() or proc_integrity_label_read() may continue operating on the dangling pointer. Researchers reported this can produce multiple exploitation primitives, including kernel memory disclosure and constrained corruption, with controlled reallocation of the freed object possible under certain conditions. Although Samsung kernel mitigations such as KCFI reduce some control-flow exploitation paths, the vulnerability can still lead to practical kernel memory corruption and potential arbitrary code execution from a local untrusted application.

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 arbitrary code execution in kernel context. Reported consequences include kernel memory disclosure that may aid KASLR bypass, constrained kernel writes, broader memory corruption primitives, and potential full device compromise. Because the flaw is in a privileged KNOX kernel component, exploitation could allow an attacker starting from a local untrusted app to gain elevated execution on the device and potentially achieve complete device takeover.

Mitigation

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

Until patched, reduce local code-execution opportunities on affected devices. Prevent installation or sideloading of untrusted applications, enforce application allowlisting and MDM policy controls, keep devices on approved builds, and restrict use of devices that are no longer receiving Samsung security updates. Because exploitation is local, enterprise controls that limit user-installed apps and maintain strong device compliance materially reduce exposure.

Remediation

Patch, then assume compromise.

Apply Samsung's January 2026 security update or later; the issue is fixed in SMR Jan-2026 Release 1 and newer. Affected organizations should verify device patch levels across Samsung Galaxy fleets, including reportedly affected S9 through S25 and A-series devices on Android 13 through 16, and ensure unsupported devices are retired or removed from sensitive use if they cannot receive the fix.
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 activity16

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