cve.bz

CVE-2022-38181 Arm Mali GPU Kernel Driver Use-After-Free Vulnerability

8.8 highKEVExploit referenceEPSS 18%

High (8.8) in Arm Mali Graphics Processing Unit (GPU). In CISA KEV since 2023-03-30. EPSS 18% estimated probability of exploitation activity in the next 30 days.

On this page
The Arm Mali GPU kernel driver allows unprivileged users to access freed memory because GPU memory operations are mishandled. This affects Bifrost r0p0 through r38p1, and r39p0; Valhall r19p0 through r38p1, and r39p0; and Midgard r4p0 through r32p0.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
18% (unchanged from 18% a week ago; 18% 30 days ago) estimated probability of exploitation activity in the next 30 days; 97th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2023-03-30, due 2023-04-20
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2025-05-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-38181 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-38181?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-38181?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-38181 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
arm:bifrost_gpu_kernel_driverfrom r0p0 through r38p1
arm:bifrost_gpu_kernel_driverr39p0
arm:midgard_gpu_kernel_driverfrom r4p0 through r31p0
arm:valhall_gpu_kernel_driverfrom r19p0 through r38p1
arm:valhall_gpu_kernel_driverr39p0

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

References

Check your stackJSON