Threats / Arm / CVE-2024-4610
CVE-2024-4610
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
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-125EPSS 0.00758 (verify live)6CVSS 7.4 (CISA)4CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported 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).
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
CVSS 7.4 (CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Arm, Mali GPU Kernel Driver. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-416 Use After Free — weakness family: Memory safety.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 5 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution 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 board1
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