How severe is CVE-2022-38181?

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

Which packages are affected by CVE-2022-38181?

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

How do I fix CVE-2022-38181?

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

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

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for :unknown:, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

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

Yes. There are 9 known exploit references for CVE-2022-38181, including 5 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-38181?

CVE-2022-38181 has an EPSS (Exploit Prediction Scoring System) score of 18.5%, placing it in the 97th 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 warrants monitoring and prompt remediation.

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

Yes. CVE-2022-38181 (Arm Mali GPU Kernel Driver Use-After-Free 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-38181?

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

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

CVE-2022-38181 was published on April 1, 2023 and was last updated on October 23, 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-38181

CVE-2022-38181 is a Use After Free vulnerability in :unknown:. It is in CISA's Known Exploited Vulnerabilities catalog (added 2023-03-30) — treat it as actively exploited and patch now. A fix is available for :unknown: — see the affected versions and patch details below.

Also known asA-259695958

Published

Apr 1, 2023

Updated

Oct 23, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

9 known

Exploitation data as of Oct 22, 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-38181.

EPSS Exploitation Probability

via FIRST.org ↗

18.5%probability of exploitation in next 30 days

Moderate Risk+4.37%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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.

Description

In kbase_mem_flags_change of mali_kbase_mem_linux.c, there is a possible way to corrupt memory due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Affected Packages

1 total 1 fixed

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

Affected Products

3 products · 5 configurations

Application

bifrost gpu kernel driverarm

≥ r0p0 && ≤ r38p1

1 version

r39p0

Application

midgard gpu kernel driverarm

≥ r4p0 && ≤ r31p0

range

Application

valhall gpu kernel driverarm

≥ r19p0 && ≤ r38p1

1 version

r39p0

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.