How severe is CVE-2022-22265?

CVE-2022-22265 has a CVSS 3.x base score of 5.0, rated medium severity. It is exploitable over local access with high attack complexity, requires low privileges and user interaction. Impact on confidentiality is low, integrity low, and availability low.

Is CVE-2022-22265 being actively exploited?

Yes. CVE-2022-22265 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2023-09-18, which means active exploitation has been confirmed. It should be prioritised for remediation.

What products are affected by CVE-2022-22265?

CVE-2022-22265 primarily affects Google Android. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2022-22265?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.

Does CVE-2022-22265 have an EU (EUVD) identifier?

Yes. CVE-2022-22265 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2022-27412. It is also flagged as exploited in the EUVD (since 2023-09-18).

When was CVE-2022-22265 published?

CVE-2022-22265 was published on 2022-01-10 and last updated on 2026-06-17.

CVE-2022-22265

CVE-2022-22265 is a medium-severity vulnerability in Google Android with a CVSS 3.x base score of 5.0. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2023-09-18). The underlying weakness is classified as CWE-703.

Key facts

Severity: Medium (CVSS 3.x base score 5.0)
CVSS v2: 4.6
EPSS exploit prediction: 0% (31st percentile)
Actively exploited: Yes — listed in CISA KEV (added 2023-09-18)
EU (EUVD) id: EUVD-2022-27412
EU exploitation: Flagged exploited in the ENISA EU Vulnerability Database (since 2023-09-18)
Weakness: CWE-703
Affected product: Google Android
Published: 2022-01-10
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2022-22265?: 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.
How severe is CVE-2022-22265?: CVE-2022-22265 has a CVSS 3.x base score of 5.0, rated medium severity. It is exploitable over local access with high attack complexity, requires low privileges and user interaction. Impact on confidentiality is low, integrity low, and availability low.
Is CVE-2022-22265 being actively exploited?: Yes. CVE-2022-22265 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2023-09-18, which means active exploitation has been confirmed. It should be prioritised for remediation.
What products are affected by CVE-2022-22265?: CVE-2022-22265 primarily affects Google Android. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2022-22265?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
Does CVE-2022-22265 have an EU (EUVD) identifier?: Yes. CVE-2022-22265 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2022-27412. It is also flagged as exploited in the EUVD (since 2023-09-18).
When was CVE-2022-22265 published?: CVE-2022-22265 was published on 2022-01-10 and last updated on 2026-06-17.

References

Affected products (4)

cpe:2.3:o:google:android:9.0:*:*:*:*:*:*:*
cpe:2.3:o:google:android:10.0:*:*:*:*:*:*:*
cpe:2.3:o:google:android:11.0:*:*:*:*:*:*:*
cpe:2.3:o:google:android:12.0:*:*:*:*:*:*:*

More vulnerabilities in Google Android

CVE-2026-0092 — Critical (CVSS 10.0): In Package Manager, there is a possible device lock controller bypass due to a missing permission check. This could…
CVE-2025-48611 — Critical (CVSS 10.0): In DeviceId of DeviceId.java, there is a possible desync in persistence due to a missing bounds check. This could lead…
CVE-2015-8073 — Critical (CVSS 10.0): mediaserver in Android 4.4 and 5.1 before 5.1.1 LMY48X allows remote attackers to execute arbitrary code or cause a…
CVE-2015-8072 — Critical (CVSS 10.0): mediaserver in Android 4.4 through 5.x before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute…
CVE-2015-6610 — Critical (CVSS 10.0): libstagefright in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows attackers to gain privileges or cause a…
CVE-2015-6609 — Critical (CVSS 10.0): libutils in Android before 5.1.1 LMY48X and 6.0 before 2015-11-01 allows remote attackers to execute arbitrary code or…

All CVEs affecting Google Android →

Other CWE-703 vulnerabilities

CVE-2025-13026 — Critical (CVSS 9.8): Sandbox escape due to incorrect boundary conditions in the Graphics: WebGPU component. This vulnerability was fixed in…
CVE-2025-13023 — Critical (CVSS 9.8): Sandbox escape due to incorrect boundary conditions in the Graphics: WebGPU component. This vulnerability was fixed in…
CVE-2025-13022 — Critical (CVSS 9.8): Incorrect boundary conditions in the Graphics: WebGPU component. This vulnerability was fixed in Firefox 145 and…
CVE-2025-13021 — Critical (CVSS 9.8): Incorrect boundary conditions in the Graphics: WebGPU component. This vulnerability was fixed in Firefox 145 and…
CVE-2024-39815 — Critical (CVSS 9.1): Improper check or handling of exceptional conditions vulnerability affecting Vonets industrial wifi bridge relays…
CVE-2023-45927 — Critical (CVSS 9.1): S-Lang 2.3.2 was discovered to contain an arithmetic exception via the function tt_sprintf().

Browse all CWE-703 vulnerabilities →