CVE-2026-0001

MEDIUMPre-NVD 4.44.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 4.4 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS
4.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.4Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (Arm Limited) lists Arm Ltd Bifrost GPU Kernel Driver versions r41p0 up to and including r49p5, r50p0 up to and including r51p0 and r54p1 up to and including r54p2; Arm Ltd Valhall GPU Kernel Driver versions r41p0 up to and including r49p5 and r50p0 up to and including r54p3; Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver versions r41p0 up to and including r49p5 and r50p0 up to and including r54p3 as affected, and Arm Ltd Valhall GPU Kernel Driver versions r56p0; Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver versions r56p0 as unaffected. No release containing a fix is confirmed on record.

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.

CVSS v3
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
20
EG Risk 20/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity44% × 45%
The EG Score, 4.4 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 8, 2026

Last Modified

September 8, 2026

Advisory Details (1)

Auto-updated Sep 8, 2026
No fix on record yet.
Web page

Documentation – Arm Developer

https://support.arm.com/documentation/111552/1-0/?lang=en

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 50× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-12 16:42 UTCEG score recompute
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-11 20:17 UTCEG score recompute
  5. 2026-10-11 16:47 UTCEG score recompute
  6. 2026-10-11 15:03 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-10-10 00:04 UTCEG score recompute
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-09 00:41 UTCEG score recompute
  12. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-10-06 23:59 UTCEG score recompute
  15. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  16. 2026-10-06 00:36 UTCEG score recompute
  17. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-10-05 01:12 UTCEG score recompute
  19. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-10-04 00:47 UTCEG score recompute
  21. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-10-03 00:35 UTCEG score recompute
  23. 2026-10-02 01:11 UTCEG score recompute
  24. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-10-01 01:45 UTCEG score recompute
Show 38 more
  1. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-09-30 02:22 UTCEG score recompute
  3. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-09-29 02:57 UTCEG score recompute
  5. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-09-28 03:33 UTCEG score recompute
  7. 2026-09-27 04:10 UTCEG score recompute
  8. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-09-26 04:46 UTCEG score recompute
  10. 2026-09-25 05:15 UTCEG score recompute
  11. 2026-09-24 05:52 UTCEG score recompute
  12. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-09-23 06:29 UTCEG score recompute
  14. 2026-09-22 07:06 UTCEG score recompute
  15. 2026-09-21 07:42 UTCEG score recompute
  16. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-09-20 08:19 UTCEG score recompute
  18. 2026-09-19 08:56 UTCEG score recompute
  19. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-09-18 09:32 UTCEG score recompute
  21. 2026-09-17 10:08 UTCEG score recompute
  22. 2026-09-16 10:44 UTCEG score recompute
  23. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-09-15 11:20 UTCEG score recompute
  25. 2026-09-14 11:57 UTCEG score recompute
  26. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  27. 2026-09-13 12:34 UTCEG score recompute
  28. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-09-12 13:09 UTCEG score recompute
  30. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  31. 2026-09-11 13:46 UTCEG score recompute
  32. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  33. 2026-09-10 14:22 UTCEG score recompute
  34. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  35. 2026-09-08 14:45 UTCEG score recomputeFirst assessed: 4.4 MEDIUM
  36. 2026-09-08 14:44 UTCMITRE cvelistV5CVSS v3 → 4.4 · severity → MEDIUM
  37. 2026-09-08 14:21 UTCEG score recompute
  38. 2026-09-08 14:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-0001?
CVE-2026-0001 is a medium-severity vulnerability; its CVE record was published on September 8, 2026. 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…
When was the CVE record for CVE-2026-0001 published?
The CVE record for CVE-2026-0001 was published on September 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-0001 actively exploited?
CVE-2026-0001 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-0001?
CVE-2026-0001 has a CVSS v3.1 base score of 4.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-0001?
No fix for CVE-2026-0001 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's CNA (Arm Limited) lists Arm Ltd Bifrost GPU Kernel Driver versions r41p0 up to and including r49p5, r50p0 up to and including r51p0 and r54p1 up to and including r54p2; Arm Ltd Valhall GPU Kernel Driver versions r41p0 up to and including r49p5 and r50p0 up to and including r54p3; Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver versions r41p0 up to and including r49p5 and r50p0 up to and including r54p3 as affected, and Arm Ltd Valhall GPU Kernel Driver versions r56p0; Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver versions r56p0 as unaffected. No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-0001

Explore →

Is Your Infrastructure Affected by CVE-2026-0001?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.