CVE Intelligence
CISA KEV High Logic error

CVE-2022-22265 — Samsung Mobile Devices Use-After-Free Vulnerability

An improper check or handling of exceptional conditions in NPU driver prior to SMR Jan-2022 Release 1 allows arbitrary memory write and code execution.

Published Jan 10, 2022 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: Samsung Mobile

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · Sep 18, 2023
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • EPSS 0.4% (30-day exploitation probability)+5
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Sep 18, 2023
EPSS FIRST
0.39%
ahead of 31% of scored CVEs · Oct 14, 2026
Affects
Google
Android and 1 more
CVSS base
7.8
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

CISA required action CISA

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

US federal deadline: Oct 9, 2023 — passed 1102 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Google Android, Samsung Mobile Samsung Mobile Devices).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes matching the vulnerability class (logic error), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Google Android version 9.0version 10.0version 11.0version 12.0 Vulnerable NIST National Vulnerability Database
Samsung Mobile Samsung Mobile Devices ≥ O(8.x), P(9.0), Q(10.0), R(11.0), S(12.0) and < SMR Jan-2022 Release 1 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.8 CVSS 3.1 High 1.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
7.8 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
5.0 CVSS 3.1 Medium 0.8 3.7 mobile.security@samsung.com via NIST National Vulnerability Database
5.0 CVSS 3.1 Medium — — Samsung Mobile via CVE Program (cve.org) e CISA ADP
4.6 CVSS 2.0 Medium 3.9 6.4 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 7.8 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-703 · Improper Check or Handling of Exceptional Conditions

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Sep 18, 2023
Federal deadline
Oct 9, 2023
passed 1102 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 0.39%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Hunt retroactively in logs from before Sep 18, 2023 (KEV listing): exploitation may have started earlier.
endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · google/android
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 5.0 → 7.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · Published → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 13, 2026
  • Affected products added · samsung mobile/samsung mobile devices
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • CVSS changed · 5.0
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2023
  • Added to CISA KEV catalog
    Sep 17, 2023 · CISA
  • 2022
  • CVE published
    Jan 10, 2022 · Samsung Mobile

Source activity

Repeated readings are counted rather than listed.

  • 3× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

Elsewhere on this site

Google
every CVE for this vendor
2023-09
what else CISA listed that month
Logic error
same class
CWE-703
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-21126 Improper input validation in getting cover image in libsimba.heifdec.media.samsung.so prior to... 3d
  • CVE-2026-21125 Improper input validation in parsing sheifd in libsimba.heifdec.media.samsung.so prior to SMR Oct... 3d
  • CVE-2026-21117 Improper access control in CocktailBarService prior to SMR Oct-2026 Release 1 allows local... 3d
  • CVE-2026-21122 Out-of-bounds write in libsamsungtts.so prior to SMR Oct-2026 Release 1 allows local attackers to... 3d
  • CVE-2026-21124 Improper input validation in getting cover image in libsimba.heifdec.media.samsung.so prior to... 3d
  • CVE-2026-21121 Improper handling of insufficient permission in CmcCore prior to SMR Oct-2026 Release 1 allows... 3d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2022-22265 is "Samsung Mobile Devices Use-After-Free Vulnerability", rated High. It affects Android (Google); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.8 describes technical severity. EPSS 0.39% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.