CVE-2023-4211: Mali GPU Kernel Driver Allows Improper GPU Memory Processing Operations
Noroxi assessment
Priority: Plan (action score 52/100)
- CISA has confirmed exploitation in the wild (Oct 3, 2023). Remediation deadline for US federal agencies: Oct 24, 2023.
- Probability of exploitation in the next 30 days: 0.97% (FIRST EPSS); higher than 62.4% of all records.
- 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.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.
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 · CISA KEV · FIRST EPSS
A local non-privileged user can make improper GPU memory processing operations to gain access to already freed memory.
- Published
- Oct 1, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.9% · 62th percentile
- CWE
- CWE-416
Report tools
Action score
52
Plan
Add it to your regular patch cycle.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 0 / 30 · 0.9%
CISA SSVC decision
- Exploitation
- active
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Oct 3, 2023. That signals real attacks, not theory.
Remediation deadline for US federal agencies: Oct 24, 2023.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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 r43p0
- arm bifrost gpu kernel driverr0p0 and later · before r43p0
- arm midgard gpu kernel driverr12p0 and later · up to r32p0 inclusive
- arm valhall gpu kernel driverr19p0 and later · before r43p0
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 r42p0affected · patch
Arm Ltd Bifrost GPU Kernel Driver
- r0p0 and later · up to and including r42p0affected · patch
Arm Ltd Midgard GPU Kernel Driver
- r12p0 and later · up to and including r32p0affected · patch
Arm Ltd Valhall GPU Kernel Driver
- r19p0 and later · up to and including r42p0affected · patch
Same product
arm: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-26083Memory leak vulnerability in Mali GPU Kernel Driver in Midgard GPU Kernel Driver all versions from r6p0 - r32p0, Bifrost GPU Kernel Driver aKEV43Plan
- CVE-2023-6143Mali GPU Kernel Driver allows improper GPU memory processing operations33Monitor
- CVE-2025-0819Mali GPU Kernel Driver allows access to already freed memory31Monitor
Published before and after this one in the same product
- Later →CVE-2023-5427Dec 1, 2023 · Mali GPU Kernel Driver allows improper GPU processing operations31Monitor
- Later →CVE-2023-32804Dec 4, 2023 · Mali GPU Userspace Driver can make an Out-of-Bounds access31Monitor
- Later →CVE-2023-5643Feb 5, 2024 · Mali GPU Kernel Driver allows improper GPU memory processing operations31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
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.
- Published
- CISA KEV+1 d
- TodayNov 10, 2026+1136 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 researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
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
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-23-0675 · Dec 5, 2023(Google Android Güvenlik Güncellemesi)
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.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&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
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.