CVE-2023-26083

Memory leak vulnerability in Mali GPU Kernel Driver in Midgard GPU Kernel Driver all versions from r6p0 - r32p0, Bifrost GPU Kernel Driver all versions from r0p0 - r42p0, Valhall GPU Kernel Driver all versions from r19p0 - r42p0, and Avalon GPU Kernel Driver all versions from r41p0 - r42p0 allows a non-privileged user to make valid GPU processing operations that expose sensitive kernel metadata.

CVSS: 3.3Lowscored by CISA
Exploited in the wild: Yes, in CISA KEV since 7 Apr 2023CISA deadline for US federal agencies: 28 Apr 2023unvetted proof-of-concept code on github
EPSS: 1.2%chance of exploitation in the next 30 daystop 31% of scored CVEsFIRST score of 11 Nov 2026
Fix: Patch availablesee the advisories in the references
Published: 6 Apr 2023analysed here 12 Nov 2026

Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)

Summary

Triage

Exploitable: At runtime
Attack vector: local
Weakness: CWE-401 Common Weakness
Can a WAF block it?: No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

arm:5th_gen_gpu_architecture_kernel_driver
arm:bifrost_gpu_kernel_driver
arm:midgard_gpu_kernel_driver
arm:valhall_gpu_kernel_driver

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog: Listed since 7 Apr 2023.
CISA due date: 28 Apr 2023, the remediation deadline for US federal agencies
CISA required action: Apply updates per vendor instructions.
Public exploit code: Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
CISA SSVC: exploitation active, automatable no, technical impact partialAssessed by CISA 19 Jan 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

GitHub proofs of concept

noverisp3/CVE-2023-260831 stars

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

6 Apr 2023Published
7 Apr 2023Added to CISA KEV (exploited in the wild)same day later
28 Apr 2023CISA remediation due date (US federal agencies)21 days later
19 Jan 2024CISA SSVC assessment: exploitation active267 days (about 9 months) later
21 Oct 2025CVE record last updated641 days (about 2 years) later
28 May 2026First proof-of-concept repository on GitHub (unvetted)218 days (about 7 months) later
12 Nov 2026Analysed by vulneraibility.com169 days (about 6 months) later

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Metric	Value	What it means
Attack vector	LocalLocal access required (shell, logged-in user).	Local access required (shell, logged-in user).
Attack complexity	LowRepeatable attack, no special conditions.	Repeatable attack, no special conditions.
Privileges required	LowThe attacker needs basic user privileges.	The attacker needs basic user privileges.
User interaction	NoneNo victim action needed.	No victim action needed.
Scope	UnchangedImpact stays within the vulnerable component.	Impact stays within the vulnerable component.
Confidentiality	LowPartial data disclosure.	Partial data disclosure.
Integrity	NoneNo unauthorised modification.	No unauthorised modification.
Availability	NoneThe service stays up.	The service stays up.

Common questions

Is CVE-2023-26083 being exploited?

Yes. CVE-2023-26083 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2023-26083?

CVE-2023-26083 is rated Low with a CVSS score of 3.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2023-26083?

Yes. A fix has been recorded for CVE-2023-26083. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2023-26083 affect?

CVE-2023-26083 affects arm:5th_gen_gpu_architecture_kernel_driver, arm:bifrost_gpu_kernel_driver, arm:midgard_gpu_kernel_driver, arm:valhall_gpu_kernel_driver. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVD CVE.org CVE Details Source

4 references in the CVE record, grouped by the tags the record gives them.

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA KEV catalog: exploitation, date added, due date
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
PoC-in-GitHub: GitHub repositories that claim a proof of concept

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.