cve.bz

CVE-2023-26083 Arm Mali GPU Kernel Driver Information Disclosure Vulnerability

3.3 lowKEVEPSS 1.2%

Low (3.3) in Arm Mali Graphics Processing Unit (GPU). In CISA KEV since 2023-04-07. EPSS 1.2% estimated probability of exploitation activity in the next 30 days.

On this page
Memory leak vulnerability in Mali GPU Kernel Driver in Midgard GPU Kernel Driver all versions from r6p0 - r32p0, Bifrost GPU Kernel Driver all versions from r0p0 - r42p0, Valhall GPU Kernel Driver all versions from r19p0 - r42p0, and Avalon GPU Kernel Driver all versions from r41p0 - r42p0 allows a non-privileged user to make valid GPU processing operations that expose sensitive kernel metadata.

Severity

CVSS 3.1

3.3 low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
1.2% (unchanged from 1.2% a week ago; 1.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 69th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2023-04-07, due 2023-04-28
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: partial, assessed 2024-01-19. 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-401 Missing Release of Memory after Effective Lifetime
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-26083 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-26083?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-26083?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-2023-26083 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:5th_gen_gpu_architecture_kernel_driverfrom r41p0 before r43p0
arm:bifrost_gpu_kernel_driverfrom r0p0 before r43p0
arm:midgard_gpu_kernel_driverfrom r6p0 through r32p0
arm:valhall_gpu_kernel_driverfrom r19p0 before r43p0

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