LiveActive security incident?Get immediate response
CVE Record

CVE-2026-20971: Use After Free in PROCA driver prior to SMR Jan-2026 Release 1 allows local attackers to potentially execut...

Use After Free in PROCA driver prior to SMR Jan-2026 Release 1 allows local attackers to potentially execute arbitrary code.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-20971 is a Samsung Mobile device vulnerability in the PROCA driver. A local attacker with low privileges could potentially execute arbitrary code. The issue is rated high severity, but exploitation requires local access, high complexity, and specific attack conditions. Samsung identifies the issue as fixed in the January 2026 SMR Release 1.

Executive priority

Treat as a high-priority mobile patching item, especially for enterprise-managed Samsung fleets. Business urgency is strongest where devices handle sensitive data or allow untrusted app installation. Current evidence does not support emergency response for active exploitation.

Technical view

The vulnerability is a use-after-free (CWE-416) in Samsung’s PROCA driver before SMR Jan-2026 Release 1. CVSS 4.0 score is 7.3 high, with local attack vector, low privileges required, no user interaction, high attack complexity, and high impact to vulnerable system confidentiality, integrity, and availability.

Likely exposure

Exposure is limited to affected Samsung Mobile Devices running Android 13, 14, 15, or 16 that have not received Samsung’s January 2026 SMR Release 1. The issue is local, so remote internet-facing exposure is not indicated by the provided sources.

Exploitation context

The sources do not report active exploitation, and the CVE is not listed as KEV in the provided data. Exploitation would require a local attacker with low privileges and specific conditions. No public exploit details are included in the source bundle.

Researcher notes

Public detail is limited to Samsung’s advisory and CVE metadata. Key constraints are AV:L, AC:H, AT:P, PR:L, and UI:N. Do not assume remote exploitability. Focus validation on Samsung patch level and whether the PROCA driver fix is included for specific models.

Mitigation direction

  • Apply Samsung Mobile January 2026 SMR Release 1 where available.
  • Prioritize managed Samsung devices that lag monthly security updates.
  • Check Samsung’s advisory for model-specific rollout and carrier timing.
  • Restrict installation of untrusted apps until devices are updated.

Validation and detection

  • Confirm device patch level includes January 2026 SMR Release 1 or later.
  • Inventory Samsung Android 13 through 16 devices in scope.
  • Verify MDM compliance reports reflect the required Samsung security update.
  • Review Samsung advisory updates for affected model details.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-20971 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 4.0HighCVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

7.3High
CVSS 4.0 vector shape for CVE-2026-20971Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Samsung MobileSamsung Mobile DevicesSMR Jan-2026 Release in Android 13, 14, 15, 16affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.