IRONSMITHINTEL
MEDIUMCVSS5.5
|
Actively Exploited
|CISA KEV|CVE-2023-4211|Auth: low — authenticated user|Reboot: required|Manual only

Arm Mali GPU Kernel Driver Use-After-Free Vulnerability (CVE-2023-4211)

Arm Mali GPU Kernel Driver contains a use-after-free vulnerability that allows a local, non-privileged user to make improper GPU memory processing operations to gain access to already freed memory.

Published Oct 1, 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 full data confidentiality loss. Federal agencies are required to remediate by 2023-10-24 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Use After Free (CWE-416) vulnerability in Arm Mali GPU Kernel Driver. A local non-privileged user can make improper GPU memory processing operations to gain access to already freed memory. 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: r12p0 ≤ 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-10-03 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2023-10-24.

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-4211'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.