LiveActive security incident?Get immediate response
CVE Record

CVE-2023-4211: Mali GPU Kernel Driver Allows Improper GPU Memory Processing Operations

A local non-privileged user can make improper GPU memory processing operations to gain access to already freed memory.

MediumCVSS 5.5Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This bug could let a local, unprivileged user read data from GPU driver memory that should no longer be accessible. It is not described as remotely exploitable, but CISA lists CVE-2023-4211 in KEV, so organizations should treat affected Mali GPU driver deployments as actively targeted.

Executive priority

Prioritize this above a normal medium CVSS item because CISA KEV indicates known exploitation. The business risk is data exposure on affected devices, especially mobile or embedded fleets where GPU driver updates depend on OEM patch channels.

Technical view

CVE-2023-4211 is a CWE-416 use-after-free in Arm Mali GPU Kernel Driver families. Improper GPU memory processing can expose already freed memory to a local low-privileged user. CVSS 3.1 is 5.5, with high confidentiality impact and no stated integrity or availability impact.

Likely exposure

Exposure is most likely on systems using Arm Mali Midgard, Bifrost, Valhall, or Arm 5th Gen GPU Architecture kernel drivers matching the versions identified in the CVE source bundle. Exact device exposure depends on OEM kernel and driver packaging.

Exploitation context

CISA KEV status supports known exploitation. The provided sources do not describe exploit mechanics, affected campaigns, or remote exploitation. The access model is local with low privileges, so risk is highest where attackers can already run code on devices.

Researcher notes

The source bundle identifies local low-privilege access, CWE-416, high confidentiality impact, and KEV status. It does not provide fixed version ranges, affected device models, proof-of-concept details, or campaign attribution, so validation should be inventory-driven and vendor-guidance based.

Mitigation direction

  • Identify devices using Arm Mali GPU Kernel Driver families named in the CVE.
  • Check Arm and OEM advisories for corrected driver or firmware packages.
  • Prioritize remediation for internet-facing fleets, mobile fleets, and shared-user devices.
  • Limit untrusted local app execution until vendor updates are applied.
  • Track CISA KEV remediation expectations where applicable.

Validation and detection

  • Inventory GPU driver family and version from vendor device records.
  • Confirm whether deployed builds include Arm Mali Midgard, Bifrost, Valhall, or 5th Gen drivers.
  • Compare deployed driver versions against Arm and OEM security guidance.
  • Verify update installation through device management or firmware compliance reporting.
  • Review endpoint telemetry for suspicious local privilege or memory-access activity.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-4211 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2023-4211Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Arm LtdMidgard GPU Kernel Driverr12p0unaffected
Arm LtdBifrost GPU Kernel Driverr0p0unaffected
Arm LtdValhall GPU Kernel Driverr19p0unaffected
Arm LtdArm 5th Gen GPU Architecture Kernel Driverr41p0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.