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

Arm Mali Graphics Processing Unit (GPU) vulnerability

Arm Mali GPU Kernel Driver contains a vulnerability allowing non-privileged users to gain write access to read-only memory pages, enabling potential privilege escalation and system compromise.

Verdict

Today item — known-exploited.

A non-privileged attacker can exploit this memory protection bypass in Mali GPU drivers to write to protected memory regions, potentially escalating privileges or corrupting kernel data structures for denial of service or code execution.

CISA KEV Yes · 2023-03-303EPSS 0.01216 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
4 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 2023-03-30).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.01216 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Arm, Mali Graphics Processing Unit (GPU). Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-119 Memory Buffer Bounds Error — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
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 execute code as an unprivileged user on a system with a vulnerable Mali GPU driver.
Business
An attacker gains a foothold on the device without requiring administrative credentials.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I exploit the memory protection bypass to write arbitrary data into read-only kernel memory regions.
Business
The organization faces risk of kernel-level compromise and loss of memory isolation guarantees.
3

Lateral reach — past segmentation narrative 3

Attacker
I corrupt kernel data structures or inject malicious code into protected memory to escalate privileges.
Business
The device is fully compromised, enabling complete system takeover and potential lateral movement.
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)
  • 4 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by mitre (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 mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.