dbcve.org
AndroidOperating system · Google

CVE-2024-23711

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 DevmemXIntUnreserveRange 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 devmemXIntUnreserveRange function in devicemem_server.c allows a local attacker to achieve arbitrary code execution in kernel context, leading to local privilege escalation without requiring any additional privileges or user interaction.

MitigationApply the vendor-supplied kernel patch or update to a fixed version that addresses the logic error in the device memory reservation handling code.

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. Verify if devmem device interface exists
    Check for /dev/mem, /dev/kmem, or device memory related entries in /dev/ using 'ls -la /dev/*mem*' or 'cat /proc/devices | grep -i mem'
    Affected if The devmem character device interface is present and accessible, providing access to physical memory which is required for the vulnerable code path to be reachable
  2. Check for device memory server functionality
    Search for devicemem_server.c or related kernel modules: 'find /system/kernel* -name "*devicemem*" 2>/dev/null' or check /proc/kallsyms for devmemXIntUnreserveRange symbol if available
    Affected if The device memory reservation handling code (devicemem_server.c with devmemXIntUnreserveRange function) is present in the kernel or associated modules
  3. Confirm Android environment
    Verify this is an Android system by checking 'getprop ro.build.id' or 'uname -a' for Android kernel identifiers
    Affected if The target system is Google Android (as stated in affected products), which is required for this vulnerability to apply
  4. Check kernel version against available patches
    Obtain kernel version via 'uname -r' or 'cat /proc/version' and compare against any Android security bulletins; since all versions are affected per the CVE, check if patches from the specific Android security patch level are applied
    Affected if The system is running any Android version without the vendor-supplied patch for CVE-2024-23711 applied to the device memory reservation handling code

A user is affected if running any version of Google Android where the devmem device interface exists and the unpatched kernel contains the vulnerable devmemXIntUnreserveRange logic error in devicemem_server.c.

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 or update to a fixed version that addresses the logic error in the device memory reservation handling code.

Recommended fix Moderate confidence

Latest Android security patch level (monthly security update) that includes kernel privilege escalation fixes

  1. Check your Android device's current security patch level in Settings > About Phone > Software Information > Security patch level
  2. Verify if your device manufacturer has released a security update that addresses this CVE (CVE-2024-23711)
  3. If an update is available, back up important data on your device
  4. Apply the security update through Settings > System > Software Update > Download and Install
  5. After updating, confirm the new security patch level includes the fix for this vulnerability
  6. For enterprise or managed devices, consult your IT administrator or Mobile Device Management (MDM) console for update deployment
Caveat Standard Android security updates typically do not introduce breaking changes to applications; kernel patches are transparent to user-facing functionality

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 / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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