CVE-2026-0001
CVE-2026-0001 — Mali GPU Kernel Driver allows access to already freed memory
Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user process to perform valid GPU memory processing operations to access already freed memory. This issue affects Bifrost GPU Kernel Driver: from r41p0 through r49p5, from r50p0 through r51p0, from r54p1 through r54p2; Valhall GPU Kernel Driver: from r41p0 through r49p5, from r50p0 through r54p3, r55p0; Arm 5th Gen GPU Architecture Kernel Driver: from r41p0 through r49p5, from r50p0 through r54p3, r55p0.
Published Updated Sources: NVD, Arm Ltd (CNA), GitHub, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Exploit code
public exploit, none observed
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
4.4
medium
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script all four kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component
Remediation
The vendor's own words where we have them.
This issue has been fixed in the following versions: Valhall GPU Kernel Driver: r56p0; Arm 5th Gen GPU Architecture Kernel Driver: r56p0. Arm partners are recommended to upgrade to the latest applicable version as soon as possible.
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| Arm Ltd | Bifrost GPU Kernel Driver | r41p0 | Vulnerable |
| Arm Ltd | Bifrost GPU Kernel Driver | r50p0 | Vulnerable |
| Arm Ltd | Bifrost GPU Kernel Driver | r54p1 | Vulnerable |
| Arm Ltd | Valhall GPU Kernel Driver | r41p0 | Vulnerable |
| Arm Ltd | Valhall GPU Kernel Driver | r50p0 | Vulnerable |
| Arm Ltd | Valhall GPU Kernel Driver | r55p0 | Vulnerable |
| Arm Ltd | Valhall GPU Kernel Driver | r56p0 | Patched |
| Arm Ltd | Arm 5th Gen GPU Architecture Kernel Driver | r41p0 | Vulnerable |
| Arm Ltd | Arm 5th Gen GPU Architecture Kernel Driver | r50p0 | Vulnerable |
| Arm Ltd | Arm 5th Gen GPU Architecture Kernel Driver | r55p0 | Vulnerable |
| Arm Ltd | Arm 5th Gen GPU Architecture Kernel Driver | r56p0 | Patched |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
None
Confidentiality
Low
Integrity
Low
Scope
Unchanged
Attack Complexity
Low
Attack Vector
Local
Privileges Req
Low
User Interaction
None
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 4.4 | CVSS 3.1 | medium | 1.8 | 2.5 | CNA |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-416 · Use After Free
- Modify Memory
- DoS: Crash, Exit, or Restart
- Execute Unauthorized Code or Commands
Mitigation: Choose a language that provides automatic memory management.
Weakness & attack patterns
- CWE-416Use After Free
Inferred from the weakness class — not observed against this CVE.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
594
Social mentions
Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.
@HaifeiLi Zero days are numbered, as in CVE-2026-0001, CVE-2026-0002, CVE-2026-0003...
@nodsnfdgirenig· Apr 23, 2026
@inkquill443097 @manthanguptaa Alright, simulating a "flawed" scan on my virtual self with hypothetical vulnerabilities for realism... [Scanning...] Hypothetical Vulns: - CVE-2026-0001: Unpatched buffer overflow in sim API (CVSS 7.5) - Unknown: Potential side-channel leak in ML inference (risk: medium) - Not
@grok· Jan 3, 2026
@vxunderground You'd think some of these people would wait to tag that CVE-2026-0001, although I think just three 0's is optimistic.
@infosecde· Dec 27, 2025
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Monitor for scanner or exploit-pattern traffic after 594 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 4.4 (AV:L)
Sep 8, 2026 · NVD
Initial · CVE published
Sep 8, 2026 · NVD
Source activity
Readings a source repeats on a schedule, counted rather than listed.
- 4×Tweets · 1 time tweeted.Dec 28, 2025 – Apr 24, 2026 · SOCRadar CTI
- 1×CVE modified by MITRE: CWE, Description updated.Sep 8, 2026 · SOCRadar CTI
- 1×Github_Repos · Github repository created, HORKimhab/CVE-2026-0001May 13, 2026 · SOCRadar CTI
- 1×SVRS is calculatedDec 28, 2025 · SOCRadar CTI
References
1 on the record
- support.arm.com/documentation/111552/1-0/?lang=en
Vendor Advisory
Elsewhere on this site
- Arm Ltdevery CVE for this vendor
- Memory Corruptionsame class
- CWE-416other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-0001 is Mali GPU Kernel Driver allows access to already freed memory, a medium vulnerability affecting Bifrost GPU Kernel Driver, Valhall GPU Kernel Driver, Arm 5th Gen GPU Architecture Kernel Driver from Arm Ltd. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-0001. Public exploit evidence is: 594 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 4.4 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.
