basicsecurity.net
Proof, not just disclosure.
Threats / Arm / CVE-2024-4610
CVE-2024-4610 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Arm Mali GPU Kernel Driver vulnerability

Arm Mali GPU Kernel Driver contains a use-after-free vulnerability allowing local non-privileged users to access freed GPU memory through improper memory processing operations.

Verdict

Today item — known-exploited.

A use-after-free flaw in Arm's Mali GPU drivers enables local attackers to manipulate GPU memory state and read sensitive data from freed allocations, posing risks to data confidentiality on affected systems.

CISA KEV Yes · 2024-06-123EPSS 0.00758 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
6 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-06-12).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.00758 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Arm, Mali GPU Kernel Driver. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-416 · Use After FreeMemory safety
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft GPU memory operations that reference already-freed memory regions to bypass access controls.
Business
Sensitive data previously stored in GPU memory becomes accessible to unprivileged processes, compromising data isolation.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I repeatedly trigger the use-after-free condition to leak cryptographic keys or authentication tokens from GPU memory.
Business
Compromised credentials enable lateral movement and unauthorized access to protected resources and services.
3

Lateral reach — past segmentation narrative 3

Attacker
I exploit the memory access to corrupt GPU state or inject malicious data into graphics processing pipelines.
Business
System stability degrades and rendering integrity is compromised, affecting dependent applications and user experience.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 6 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by Arm (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by ArmCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.