CVE-2024-6790: Mali GPU Kernel Driver can cause the whole system to become unresponsive
Noroxi assessment
Priority: Monitor (action score 24/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.15% (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 Arm 5th Gen GPU Architecture Kernel Driver r49p1, r52p0; Arm Ltd Bifrost GPU Kernel Driver r49p1; Arm Ltd Valhall GPU Kernel Driver r49p1, r52p0.
Low priority for now. Upgrade to Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver r49p1, r52p0; Arm Ltd Bifrost GPU Kernel Driver r49p1; Arm Ltd Valhall GPU Kernel Driver r49p1, r52p0 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
Loop with Unreachable Exit Condition ('Infinite Loop') 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 non-privileged user process to make valid GPU memory processing operations, including via WebGL or WebGPU, to cause the whole system to become unresponsive.This issue affects Bifrost GPU Kernel Driver: r44p1, from r46p0 through r49p0, from r50p0 through r51p0; Valhall GPU Kernel Driver: r44p1, from r46p0 through r49p0, from r50p0 through r51p0; Arm 5th Gen GPU Architecture Kernel Driver: r44p1, from r46p0 through r49p0, from r50p0 through r51p0.
- Published
- Feb 3, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-835
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
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
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 | 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 driverr46p0 and later · before r49p1
- arm 5th gen gpu architecture kernel driverr50p0 and later · before r52p0
- arm 5th gen gpu architecture kernel driverr44p1
- arm bifrost gpu kernel driverr46p0 and later · before r49p1
- arm bifrost gpu kernel driverr50p0 and later · up to r51p0 inclusive
- arm bifrost gpu kernel driverr44p1
- arm valhall gpu kernel driverr46p0 and later · before r49p1
- arm valhall gpu kernel driverr50p0 and later · before r52p0
- arm valhall gpu kernel driverr44p1
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
- r44p1affected
- r46p0 and later · up to and including r49p0affected · patchfixed in r49p1
- r50p0 and later · up to and including r51p0affected · patchfixed in r52p0
Arm Ltd Bifrost GPU Kernel Driver
- r44p1affected
- r46p0 and later · up to and including r49p0affected · patchfixed in r49p1
- r50p0 and later · up to and including r51p0affected · patch
Arm Ltd Valhall GPU Kernel Driver
- r44p1affected
- r46p0 and later · up to and including r49p0affected · patchfixed in r49p1
- r50p0 and later · up to and including r51p0affected · patchfixed in r52p0
Same product
arm: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-4211Mali GPU Kernel Driver Allows Improper GPU Memory Processing OperationsKEV52Plan
- 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
Published before and after this one in the same product
- ← EarlierCVE-2024-4607Aug 5, 2024 · Mali GPU Kernel Driver allows improper GPU memory processing operations31Monitor
- ← EarlierCVE-2024-3655Sep 3, 2024 · Mali GPU Kernel Driver allows improper GPU memory processing operations31Monitor
- Later →CVE-2025-0015Feb 3, 2025 · Mali GPU Kernel Driver allows improper GPU 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.
| Product / package | Fixed version | Source |
|---|---|---|
| Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver | r49p1 | Vendor (CNA) |
| Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver | r52p0 | Vendor (CNA) |
| Arm Ltd Bifrost GPU Kernel Driver | r49p1 | Vendor (CNA) |
| Arm Ltd Valhall GPU Kernel Driver | r49p1 | Vendor (CNA) |
| Arm Ltd Valhall GPU Kernel Driver | r52p0 | 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.
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 researchersFinders, 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
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.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- High
Weakness class (CWE)
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
nvd-primary
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✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.