dbcve.org
AndroidOperating system · Google

CVE-2024-23697

HIGH · 7.8 CVSS v3.1 Published 2024-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In RGXCreateHWRTData_aux of rgxta3d.c, there is a possible arbitrary code execution due to a use after free. This could lead to local escalation of privilege in the kernel with no additional execution privileges needed. User interaction is not needed for exploitation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A use-after-free vulnerability exists in the RGXCreateHWRTData_aux function within the rgxta3d.c kernel-mode graphics driver (PowerVR RGX). The vulnerability allows a local attacker to achieve arbitrary code execution in kernel context through a dangling pointer after memory is freed, enabling local privilege escalation without requiring additional privileges or user interaction.

MitigationApply the vendor-supplied driver update/patch for the PowerVR RGX graphics driver to fix the use-after-free in RGXCreateHWRTData_aux. Until patched, monitor for indicators of compromise targeting kernel driver vulnerabilities.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify PowerVR RGX GPU presence
    Check if the device uses Imagination Technologies PowerVR GPU by inspecting /proc/pvr/version or looking for PowerVR-related modules in /proc/modules, or checking dmesg for 'PowerVR' or 'RGX' strings
    Affected if The device has a PowerVR RGX GPU and the vulnerable graphics driver is loaded
  2. Locate the graphics driver module
    Search for driver files matching 'rgxta3d' or 'pvrsrv' patterns in /vendor/lib/modules, /vendor/lib, or /system/lib directories using 'find' or 'ls'
    Affected if The rgxta3d driver file is present on the device, indicating the vulnerable code path exists
  3. Extract driver version information
    If available, read version metadata from the driver module using strings grep or parse /proc/pvr/version output for build/revision numbers
    Affected if Unable to obtain a fixed version from the vendor, indicating the unpatched driver is in use
  4. Check for kernel indicators of exploitation
    Review kernel logs (dmesg, /proc/kmsg) for memory corruption indicators, unexpected kernel oops/panics, or suspicious module loading related to the graphics driver
    Affected if Kernel debugging shows signs of use-after-free memory corruption in graphics driver context or unexplained privilege escalation behavior
  5. Verify vendor security patch level
    Check the Android security patch level in Settings > About Phone > Security Patch Level or via 'getprop ro.build.version.security_patch'
    Affected if The device security patch level is earlier than the vendor release containing the CVE-2024-23697 fix for PowerVR RGX driver

The device is affected if it contains the PowerVR RGX graphics driver (rgxta3d) and has not received the vendor-supplied patch addressing the use-after-free vulnerability in RGXCreateHWRTData_aux.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied driver update/patch for the PowerVR RGX graphics driver to fix the use-after-free in RGXCreateHWRTData_aux. Until patched, monitor for indicators of compromise targeting kernel driver vulnerabilities.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23697 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23697 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data