CVE-2023-26083
Arm 5Th Gen Gpu Architecture Kernel Driver r41p0 – r43p0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2023-26083 is a low-severity Missing Release of Memory after Effective Lifetime (CWE-401) vulnerability in Arm 5Th Gen Gpu Architecture Kernel Driver. Its CVSS base score is 3.3 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked in the top 33% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-26083 is a memory leak vulnerability (CWE-401) in the Mali GPU Kernel Driver. It affects Midgard GPU Kernel Driver versions r6p0 through r32p0, Bifrost versions r0p0 through r42p0, Valhall versions r19p0 through r42p0, and Avalon versions r41p0 through r42p0. The flaw permits a non-privileged user to perform valid GPU processing operations that leak sensitive kernel metadata, rated at CVSS 3.3 with local attack vector and low complexity.
A local attacker with a non-privileged account on an affected system can trigger the vulnerability through legitimate GPU operations, resulting in exposure of kernel metadata without requiring elevated privileges or user interaction.
Advisories from Arm and related vulnerability databases, referenced at developer.arm.com and cybersecurity-help.cz, provide further details on affected driver versions and recommended updates. The EPSS score remains low, with a current value of 0.0523 and a peak of 0.0733.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-29957
Vulnerability Data
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…
more
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.
- CWE(s)
- KEV Date Added
- 07 April 2023
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly enforce proper memory allocation/deallocation via coding standards, reviews, and tooling.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect unreleased memory, providing partial coverage of the weakness.
Secure development life cycle mandates memory-management practices that reduce missing-release defects.
Application security requirements can specify explicit memory-release rules, partially mitigating the weakness.
Secure system architecture and engineering principles include resource-management guidelines that address memory leaks.
Secure coding standards directly require proper allocation/deallocation, covering most of this weakness.
Capacity management may detect memory exhaustion symptoms but does not prevent the coding flaw.