How severe is CVE-2022-22706?

No CVSS score has been assigned to CVE-2022-22706 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2022-22706?

CVE-2022-22706 affects the following packages: :unknown: (Android). Ecosystems affected: Android.

How do I fix CVE-2022-22706?

Update :unknown: to SoCVersion:2023-06-05 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-22706 is resolved across your whole dependency graph.

How do I detect CVE-2022-22706 in my Android dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for :unknown:. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2022-22706 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2022-22706?

O3 pinpoints whether CVE-2022-22706 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Yes. There are 2 known exploit references for CVE-2022-22706, including 2 in-the-wild exploitations 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-22706?

CVE-2022-22706 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 63th 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-22706 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2022-22706 (Arm Mali GPU Kernel Driver Unspecified Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-03-30. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-04-20. The required action was: Apply updates per vendor instructions. 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-22706?

CVE-2022-22706 is classified as Buffer Overflow (CWE-119). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2022-22706 was published on June 1, 2023 and was last updated on September 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Android

CISA KEV · ACTIVELY EXPLOITED

CVE-2022-22706

CVE-2022-22706 is a Buffer Overflow vulnerability in :unknown:. It is in CISA's Known Exploited Vulnerabilities catalog (added 2023-03-30) — treat it as actively exploited and patch now. O3 Security confirms whether CVE-2022-22706 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Also known asA-225040268

Published

Jun 1, 2023

Updated

Sep 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Aug 25, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2023-03-30. Federal agencies were required to remediate by 2023-04-20.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2022-22706.

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk-0.08%

Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

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.

Real-World Exposure

1 pkg affected

📦:unknown:

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Android packages — download data is not available via public APIs for these ecosystems.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Android	`:unknown:`	≥ SoCVersion:0&&< SoCVersion:2023-06-05	SoCVersion:2023-06-05

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.

Arm Mali GPU Kernel Driver allows a non-privileged user to achieve write…

developer.arm.comAPIApr 2022

Arm Mali GPU Kernel Driver allows a non-privileged user to achieve write…

cisa.govCISAMar 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for :unknown:. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update :unknown: to SoCVersion:2023-06-05 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-22706 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2022-22706 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2022-22706. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

CVE-2022-22706 is a security vulnerability affecting open source software. Review affected packages and apply the recommended fix as soon as possible.

O3 Security · Impact-Aware SCA

Is CVE-2022-22706 in your dependencies?

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

Scan my dependencies How O3 SCA works