How severe is CVE-2024-4610?

No CVSS score has been assigned to CVE-2024-4610 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-4610?

CVE-2024-4610 affects the following packages: :unknown: (Android). Ecosystems affected: Android.

How do I fix CVE-2024-4610?

Update :unknown: to SoCVersion:2024-07-05 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-4610 is resolved across your whole dependency graph.

How do I detect CVE-2024-4610 in my Android dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for :unknown:, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-4610 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2024-4610 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2024-4610, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-4610?

CVE-2024-4610 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2024-4610 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2024-4610 (Arm Mali GPU Kernel Driver Use-After-Free Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2024-06-12. CISA required all US federal civilian agencies to remediate this vulnerability by 2024-07-03. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2024-4610?

CVE-2024-4610 is classified as Use After Free (CWE-416). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-4610 published, and has it been updated?

CVE-2024-4610 was published on July 1, 2024 and was last updated on October 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Android

CISA KEV · ACTIVELY EXPLOITED

CVE-2024-4610

CVE-2024-4610 is a Use After Free vulnerability in :unknown:. It is in CISA's Known Exploited Vulnerabilities catalog (added 2024-06-12) — treat it as actively exploited and patch now. A fix is available for :unknown: — see the affected versions and patch details below.

Also known asA-260126994

Published

Jul 1, 2024

Updated

Oct 23, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2024-06-12. Federal agencies were required to remediate by 2024-07-03.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2024-4610.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

📦:unknown:

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Android packages — download data is not available via public APIs for these ecosystems.

Description

Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm Ltd Valhall GPU Kernel Driver allows a local non-privileged user to make improper GPU memory processing operations to gain access to already freed memory.This issue affects Bifrost GPU Kernel Driver: from r34p0 through r40p0; Valhall GPU Kernel Driver: from r34p0 through r40p0.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Android	`:unknown:`	≥ SoCVersion:0&&< SoCVersion:2024-07-05	SoCVersion:2024-07-05

Affected Products

2 products · 2 configurations

Application

bifrost gpu kernel driverarm

≥ r34p0 && < r41p0

range

Application

valhall gpu kernel driverarm

≥ r34p0 && < r41p0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm L…

developer.arm.comGoogle-sheetJun 2024

Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel Driver, Arm L…

cisa.govCISAJun 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for :unknown:, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update :unknown: to SoCVersion:2024-07-05 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-4610 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

CVE-2024-4610 is a security vulnerability affecting open source software. Review affected packages and apply the recommended fix as soon as possible.

O3 Security · Impact-Aware SCA

Is CVE-2024-4610 in your dependencies?

Find it across Android, including transitive dependencies.

Scan my dependencies How O3 SCA works