IRONSMITHINTEL
LOWCVSS3.3
|
Actively Exploited
|CISA KEV|CVE-2023-26083|Auth: low — authenticated user|Reboot: required|Manual only

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

Arm Mali GPU Kernel Driver contains an information disclosure vulnerability that allows a non-privileged user to make valid GPU processing operations that expose sensitive kernel metadata.

Published Apr 6, 2023 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A local attacker, with a low-privilege account, can achieve partial data exposure. Federal agencies are required to remediate by 2023-04-28 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Software Vulnerability (CWE-401) (CWE-401) vulnerability in Arm Mali Graphics Processing Unit (GPU). 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. Exploitation requires local access, low attack complexity, a low-privilege authenticated account, and no user interaction required.

Am I affected?Quick check

Probably yes if any of these apply:

●IT Security
●Running 5th gen gpu architecture kernel driver: r41p0 ≤ v < r43p0; bifrost gpu kernel driver: r0p0 ≤ v < r43p0; midgard gpu kernel driver: r6p0 ≤ v ≤ r32p0; valhall gpu kernel driver: r19p0 ≤ v < r43p0
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2023-04-07 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2023-04-28.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for general installs in scope.
2
Apply the vendor security update referenced in CVE-2023-26083's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.

References

↗ CVE-2023-26083↗ MSRC Advisory↗ NVD↗ Vendor Advisory