NVD / CVE Program· CNA Arm

CVE-2023-6241: Mali GPU Kernel Driver allows improper GPU memory processing operations

Noroxi assessment

Priority: Monitor (action score 28/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 0.71% (FIRST EPSS); higher than 53.9% of all records.
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver r47p0; Arm Ltd Bifrost GPU Kernel Driver r26p0; Arm Ltd Valhall GPU Kernel Driver r26p0, r47p0.

Low priority for now. Upgrade to Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver r47p0; Arm Ltd Bifrost GPU Kernel Driver r26p0; Arm Ltd Valhall GPU Kernel Driver r26p0, r47p0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Use After Free vulnerability in Arm Ltd Midgard GPU Kernel Driver, 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 to exploit a software race condition to perform improper memory processing operations. If the system’s memory is carefully prepared by the user, then this in turn cause a use-after-free.This issue affects Midgard GPU Kernel Driver: from r13p0 through r32p0; Bifrost GPU Kernel Driver: from r11p0 through r25p0; Valhall GPU Kernel Driver: from r19p0 through r25p0, from r29p0 through r46p0; Arm 5th Gen GPU Architecture Kernel Driver: from r41p0 through r46p0.

HighCVSS 7.0 · v3.1—Proof of concept Fix available

BDU:2024-02696

Published: Mar 4, 2024
Updated: Jun 17, 2026
EPSS: 0.7% · 53th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.0 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.7%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
arm	5th gen gpu architecture kernel driver	cpe:2.3:a:arm:5th_gen_gpu_architecture_kernel_driver
arm	bifrost gpu kernel driver	cpe:2.3:a:arm:bifrost_gpu_kernel_driver
arm	midgard gpu kernel driver	cpe:2.3:a:arm:midgard_gpu_kernel_driver
arm	valhall gpu kernel driver	cpe:2.3:a:arm:valhall_gpu_kernel_driver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

arm 5th gen gpu architecture kernel driverr41p0 and later · before r47p0
arm bifrost gpu kernel driverr11p0 and later · before r26p0
arm midgard gpu kernel driverr13p0 and later · up to r32p0 inclusive
arm valhall gpu kernel driverr19p0 and later · before r26p0
arm valhall gpu kernel driverr29p0 and later · before r47p0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Arm). Independent of NVD's CPE analysis and usually ahead of it.

Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver
- r41p0 and later · up to and including r46p0affected · patchfixed in r47p0
Arm Ltd Bifrost GPU Kernel Driver
- r11p0 and later · up to and including r25p0affected · patchfixed in r26p0
Arm Ltd Midgard GPU Kernel Driver
- r13p0 and later · up to and including r32p0affected · patch
Arm Ltd Valhall GPU Kernel Driver
- r19p0 and later · up to and including r25p0affected · patchfixed in r26p0
- r29p0 and later · up to and including r46p0affected · patchfixed in r47p0

Same product

arm: all records

Other highest-scoring records for the same primary product.

CVE-2023-4211Mali GPU Kernel Driver Allows Improper GPU Memory Processing OperationsKEV
52Plan
CVE-2023-26083Memory leak vulnerability in Mali GPU Kernel Driver in Midgard GPU Kernel Driver all versions from r6p0 - r32p0, Bifrost GPU Kernel Driver aKEV
43Plan
CVE-2023-6143Mali GPU Kernel Driver allows improper GPU memory processing operations
33Monitor

Published before and after this one in the same product

← EarlierCVE-2023-32804Dec 4, 2023 · Mali GPU Userspace Driver can make an Out-of-Bounds access
31Monitor
← EarlierCVE-2023-5643Feb 5, 2024 · Mali GPU Kernel Driver allows improper GPU memory processing operations
31Monitor
Later →CVE-2024-0671Apr 19, 2024 · Mali GPU Kernel Driver allows improper GPU memory processing operations
27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver	r47p0	Vendor (CNA)
Arm Ltd Bifrost GPU Kernel Driver	r26p0	Vendor (CNA)
Arm Ltd Valhall GPU Kernel Driver	r26p0	Vendor (CNA)
Arm Ltd Valhall GPU Kernel Driver	r47p0	Vendor (CNA)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:17	2024-05-02
Proof-of-concept repository on GitHub	stars:15	2024-09-17

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedMar 4, 2024
First PoCMay 2, 2024+59 d
TodayNov 8, 2026+979 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Man Yue MoGitHub Security Labfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2023-4211155 days apartMali GPU Kernel Driver Allows Improper GPU Memory Processing OperationsKEV
52Plan
CVE-2023-61430 days apartMali GPU Kernel Driver allows improper GPU memory processing operations
33Monitor
CVE-2023-542794 days apartMali GPU Kernel Driver allows improper GPU processing operations
31Monitor
CVE-2024-2937154 days apartMali GPU Kernel Driver allows improper GPU memory processing operations
31Monitor
CVE-2024-4607154 days apartMali GPU Kernel Driver allows improper GPU memory processing operations
31Monitor
CVE-2024-3655183 days apartMali GPU Kernel Driver allows improper GPU memory processing operations
31Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

ArmIntigriti · paid · up to $20,000

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: High
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

For records you follow, these changes also arrive as notifications. →

References

developer.arm.com/Arm%20Security%20Center/Mali%20GPU%20Driver%20Vulnerabilities

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records