Home › Intelligence › Brief
VULNERABILITY BRIEF🟠 High Vulnerability

CVE‑2023‑4211: Arm Mali GPU Kernel Driver Use‑After‑Free Vulnerability Enables Local Memory Access

A use‑after‑free flaw in the Arm Mali GPU kernel driver (CVE‑2023‑4211) allows a non‑privileged user to read freed GPU memory. The issue underscores the need for continuous driver patching and evidence of secure configuration for audit readiness.

LiveThreat™ Intelligence · 📅 October 07, 2026· 📰 nvd.nist.gov
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
2 sector(s)
✅
Actions
5 recommended
📰
Source
nvd.nist.gov

CVE‑2023‑4211: Arm Mali GPU Kernel Driver Use‑After‑Free Vulnerability

What It Is – The Arm Mali GPU kernel driver contains a use‑after‑free flaw that lets a local, non‑privileged user trigger improper GPU memory processing and read memory that has already been freed.

Exploitability – The vulnerability is exploitable locally without special privileges; a proof‑of‑concept exists. CVSS v3.1 base score is 7.8 (High).

Affected Products – Arm Mali GPU kernel driver across devices that ship the driver (smartphones, tablets, embedded IoT, automotive infotainment, and other Linux‑based platforms).

Why It Matters for Trust & Control Assurance

  • Continuous control monitoring – Detecting unpatched driver versions in your asset inventory is essential evidence of an active patch‑management program.
  • Defensible audit trail – Demonstrating timely remediation of a kernel‑level memory‑isolation flaw satisfies control objectives around access control and secure configuration, which map to multiple frameworks (e.g., NIST CSF 2.0).
  • Supply‑chain due diligence – The driver is a third‑party component; maintaining provenance and verification of updates shows robust vendor‑risk oversight.

Recommended Actions

  • Identify all endpoints running the Arm Mali GPU driver and record the driver version.
  • Apply the vendor‑released patch or upgrade to a fixed driver version as soon as it is available.
  • Validate that the patched driver is loaded correctly and that no legacy versions remain on the system.
  • Integrate driver‑version checks into your continuous monitoring platform to generate evidence of ongoing compliance.
  • Document the remediation steps in your change‑management system to create a defensible audit record.

Source: CISA KEV – CVE‑2023‑4211

📰 Original Source
https://nvd.nist.gov/vuln/detail/CVE-2023-4211 ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Could you prove your access controls held up here?

Credential and access failures map directly to identity and access-control requirements in every major framework. The Verisq AI Trust Operations platform shows where your evidence is thin before an auditor — or an attacker — finds out.

Explore the Verisq AI Trust Operations platform →