How severe is CVE-2022-22265?

CVE-2022-22265 has a CVSS score of 5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-22265?

Affected package information for CVE-2022-22265 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2022-22265?

No fixed version has been published for CVE-2022-22265 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2022-22265 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-22265, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-22265?

CVE-2022-22265 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 36th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2022-22265 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2022-22265 (Samsung Mobile Devices Use-After-Free Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-09-18. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-10-09. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2022-22265?

CVE-2022-22265 is classified as CWE-703 (CWE-703). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2022-22265?

CVE-2022-22265 affects google android (4 versions, e.g. 9.0, 10.0, 11.0…). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2022-22265 published, and has it been updated?

CVE-2022-22265 was published on January 10, 2022 and was last updated on October 30, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2023-09-18 — agencies required to remediate by 2023-10-09

CVE-2022-22265

MEDIUM

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 30, 2025

Affected

0 pkgs

Patched

None yet

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk36th percentile-0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

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.

Affected Products

1 product · 4 configurations

androidgoogle

4 versions

9.010.011.012.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An improper check or handling of exceptional conditions in NPU driver pr…

cisa.govCISASep 2023

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2022-22265 in your stack?

O3 detects CVE-2022-22265 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works