dbcve.org
AndroidOperating system · Google

CVE-2024-31336

HIGH · 7.8 CVSS v3.1 Published 2024-09-11
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 PVRSRVBridgeRGXKickTA3D2 of server_rgxta3d_bridge.c, there is a possible arbitrary code execution due to improper input validation. 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 · high confidence

A vulnerability exists in the PVRSRVBridgeRGXKickTA3D2 function within server_rgxta3d_bridge.c where improper input validation allows local privilege escalation to kernel level, potentially enabling arbitrary code execution without requiring additional privileges or user interaction.

MitigationApply vendor-provided patches for the PowerVR Graphics driver; update to the latest version containing the input validation fixes in the PVRSRVBridgeRGXKickTA3D2 bridge function.

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 if the device runs Android
    Check /system/build.prop for ro.build.version.sdk or run 'getprop ro.build.version.sdk'
    Affected if The device is not running Android (this CVE only affects Android)
  2. Check for PowerVR Graphics driver presence
    Look for PowerVR kernel modules: ls /system/lib/modules/ | grep -i pvrsrvgx or check /proc/pvrsrgx for driver info
    Affected if No PowerVR driver components are found on the device (not affected if no PowerVR GPU/driver)
  3. Get the PowerVR driver version
    Check /sys/module/pvrsrgxsys_kgdb/parameters/version or examine driver files in /vendor/lib/hw/ for pvrsrgx* files
    Affected if Driver version cannot be determined or is present on all Android versions per vendor advisory
  4. Verify the vulnerable bridge function is exposed
    Check for existence of /dev/pvrsrgx or similar device nodes used by PVRSRVBridgeRGXKickTA3D2: ls -la /dev/pvrs* 2>/dev/null
    Affected if The bridge device interface exists and is accessible to local users

The device is affected if it runs Android with a PowerVR Graphics driver that exposes the PVRSRVBridgeRGXKickTA3D2 bridge function, as all Android versions with this driver are impacted per the vendor advisory.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches for the PowerVR Graphics driver; update to the latest version containing the input validation fixes in the PVRSRVBridgeRGXKickTA3D2 bridge function.

Recommended fix Moderate confidence

Android Security Patch Level 2024-03-05 or later (check source.android.com/security/bulletin for specific patch date)

  1. 1. Identify your Android device model and check if your device manufacturer has released a security update that includes the fix for CVE-2024-31336
  2. 2. Go to your device Settings > Security (or System > Security) and check the current Android security patch level
  3. 3. If your device is not running the latest security patch level, initiate a system update to install the latest available Android security update
  4. 4. For enterprise or managed devices, contact your IT administrator to ensure the latest Android security bulletin patches have been deployed
  5. 5. If your device manufacturer has not released an update, consider upgrading to a newer device model that receives active security support
Caveat Device must still receive monthly security updates from manufacturer; older devices may not receive patches

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31336 — 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-31336 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