LiveActive security incident?Get immediate response
CVE Record

CVE-2022-22265: An improper check or handling of exceptional conditions in NPU driver prior to SMR Jan-2022 Release 1 allow...

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.

MediumCVSS 5Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Samsung mobile device flaw is in the NPU driver and can allow arbitrary memory writes and code execution. The base CVSS is medium because exploitation needs local access, low privileges, high complexity, and user interaction. Business urgency is higher because CISA lists it in KEV, indicating confirmed exploitation.

Executive priority

Treat this as a near-term mobile remediation item. The technical score is medium, but KEV status means exploitation has been observed. Prioritize managed Samsung fleets, executive devices, and any unsupported models that cannot be patched.

Technical view

CVE-2022-22265 is CWE-703: improper handling of exceptional conditions in Samsung's NPU driver. Samsung reports affected devices running Android O through S before SMR Jan-2022 Release 1. The CVSS vector is local, high complexity, low privileges, user interaction required, scope changed, with low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to Samsung Mobile Devices on Android 8.x through 12.0 that have not received SMR Jan-2022 Release 1 or later. The provided sources do not identify specific device models, carrier variants, or chipset dependencies.

Exploitation context

Active exploitation is supported by the CISA KEV listing. The sources do not provide exploit details, target patterns, or campaign context. The CVSS vector indicates exploitation is local and requires user interaction, which reduces broad remote wormability but does not remove targeted-device risk.

Researcher notes

The source bundle confirms impact, affected Android major versions, CVSS, CWE, and KEV status. It does not provide model-level affected lists, exploit primitives beyond arbitrary memory write and code execution, or independent mitigation options beyond Samsung's January 2022 security release.

Mitigation direction

  • Apply Samsung SMR Jan-2022 Release 1 or later where available.
  • Prioritize Samsung devices still running Android O, P, Q, R, or S.
  • Check Samsung and carrier guidance for unsupported or delayed-update devices.
  • Retire or isolate devices that cannot receive the fixed release.

Validation and detection

  • Inventory Samsung mobile devices by Android version and security patch level.
  • Confirm each device has SMR Jan-2022 Release 1 or later installed.
  • Use MDM compliance policies to flag older Samsung patch levels.
  • Review CISA KEV applicability for remediation tracking and reporting.
Prepared
Confidence
medium
Sources
4

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-703: 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-2022-22265 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
Medium
CVSS
5 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L

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
3Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

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
5CVSS 3.1MediumCVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L0.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5Medium
CVSS 3.1 vector shape for CVE-2022-22265Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Samsung MobileSamsung Mobile DevicesO(8.x), P(9.0), Q(10.0), R(11.0), S(12.0)Listed
Weakness

CWE details

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

CWE-703 · source CWE mapping

Improper Check or Handling of Exceptional Conditions

Improper Check or Handling of Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.