Threats / Arm / CVE-2023-26083
CVE-2023-26083
· 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 an information disclosure vulnerability allowing non-privileged users to expose sensitive kernel metadata through valid GPU processing operations.
Verdict
Today item — known-exploited.
A local information disclosure flaw in Mali GPU drivers permits unprivileged attackers to leak kernel memory contents via GPU operations, potentially enabling privilege escalation or further system compromise.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
7 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-04-07).
Probability (EPSS)
EPSS 0.01417 — 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.
Weakness (CWE)
Mapped to CWE-401 CWE-401 — weakness family: Resource / availability.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
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
Execute GPU processing operations as a non-privileged local user to trigger kernel metadata exposure.
Business
Sensitive kernel information becomes accessible to local users, reducing security isolation boundaries.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
Harvest exposed kernel metadata to identify memory layout, function addresses, or other kernel internals for exploitation.
Business
Kernel address space layout randomization and other mitigations become less effective, increasing privilege escalation risk.
3
Lateral reach — past segmentation narrative 3
Attacker
Chain information disclosure with other vulnerabilities to achieve unauthorized system access or data exfiltration.
Business
System confidentiality and integrity are compromised, potentially affecting all data and processes on affected devices.
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