dbcve.org
AndroidOperating system · Google

CVE-2024-31334

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 DevmemIntFreeDefBackingPage of devicemem_server.c, there is a possible arbitrary code execution due to a logic error in the code. 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 logic error in the DevmemIntFreeDefBackingPage function in devicemem_server.c allows arbitrary kernel code execution, enabling local privilege escalation without requiring additional privileges or user interaction.

MitigationApply the vendor-supplied kernel patch addressing the logic error in devicemem_server.c; this typically involves updating the Linux kernel to a patched version.

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. Check kernel version on the Android device
    Run 'uname -a' or read '/proc/version' to obtain the running kernel version string
    Affected if The kernel version is an unpatched version of the Android kernel that contains the vulnerable devicemem_server.c logic error (Android versions prior to vendor patch availability)
  2. Verify if the devicemem kernel module or functionality is present
    Check for the presence of '/dev/ion' or similar devicemem-related device nodes and kernel symbols; also check '/sys/module' for devicemem or ion-related modules
    Affected if The devicemem functionality is enabled in the kernel, as the vulnerability exists in DevmemIntFreeDefBackingPage function in devicemem_server.c
  3. Check kernel configuration for devicemem support
    If you have access to the kernel config (often in /boot/config-* or /proc/config.gz), search for CONFIG_DEVICEMEM or similar devicemem/ion configuration options
    Affected if The kernel has CONFIG_DEVICEMEM or related memory management features enabled, which exposes the vulnerable code path

If the Android device runs a kernel version that predates the vendor security patch for CVE-2024-31334 AND has devicemem functionality present, the device is affected by this privilege escalation vulnerability.

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 the vendor-supplied kernel patch addressing the logic error in devicemem_server.c; this typically involves updating the Linux kernel to a patched version.

Recommended fix Moderate confidence

Apply Android security patch level that includes the fix for CVE-2024-31334 (check Android Security Bulletin for specific date)

  1. 1. Check the Android Security Bulletin for the month this CVE was addressed (refer to source.android.com/security-bulletin)
  2. 2. Identify the Android security patch level that includes the fix for this vulnerability
  3. 3. Apply the monthly security update to your Android device via system updates
  4. 4. Verify the device has the correct security patch level installed in Settings > About Phone > Android version (should show the patched security level)
  5. 5. For developers building custom kernels: apply the kernel source patch to devicemem_server.c in the Android kernel source tree, specifically fixing the logic error in DevmemIntFreeDefBackingPage function
Caveat Monthly security updates are cumulative; applying the update includes all security patches for that month and should not introduce functional breaking changes

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-31334 — 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-31334 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