CVE-2023-3889· NVD / CVE Program· CNA Arm

Mali GPU Kernel Driver exposes sensitive data from freed memory

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Arm Ltd Valhall GPU Kernel Driver r44p1, r45p0.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Arm Ltd Valhall GPU Kernel Driver r44p1, r45p0 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

A local non-privileged user can make improper GPU memory processing operations. If the operations are carefully prepared, then they could be used to gain access to already freed memory.

HighCVSS 7.8 · v3.1—No exploit Fix available

Published: Nov 7, 2023
Updated: Jun 17, 2026
EPSS: 0.1% · 7th percentile
CWE: CWE-119

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
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
No public exploit code on record
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	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 valhall gpu kernel driverr38p0 and later · up to r44p0 inclusive

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 Valhall GPU Kernel Driver
- r38p0 and later · up to and including r44p0affected · patchfixed in r44p1, r45p0

Same product

arm: all records

Other highest-scoring records for the same primary product.

CVE-2022-28350Arm Mali GPU Kernel Driver allows improper GPU operations in Valhall r29p0 through r36p0 before r37p0 to reach a use-after-free situation.
39Monitor
CVE-2022-42716An issue was discovered in the Arm Mali GPU Kernel Driver.
35Monitor
CVE-2022-41757An issue was discovered in the Arm Mali GPU Kernel Driver.
35Monitor

Published before and after this one in the same product

← EarlierCVE-2022-33917Aug 2, 2022 · An issue was discovered in the Arm Mali GPU Kernel Driver (Valhall r29p0 through r38p0).
22Monitor
Later →CVE-2023-5091Jan 8, 2024 · Mali GPU Kernel Driver allows improper GPU processing operations
22Monitor

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 Valhall GPU Kernel Driver	r44p1	Vendor (CNA)
Arm Ltd Valhall GPU Kernel Driver	r45p0	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

No credits in the CNA record.

Variant candidates

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

No nightly-computed relations.

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