dbcve.org
AndroidOperating system · Google

CVE-2024-34729

HIGH · 7.8 CVSS v3.1 Published 2024-11-13
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 multiple locations, 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 kernel code across multiple locations allows an attacker to execute arbitrary code with kernel-level privileges, achieving local privilege escalation without requiring additional execution privileges or user interaction.

MitigationApply the vendor-supplied kernel patch addressing the logic error in the affected code locations; given the kernel-level scope, this requires a system reboot to load the patched kernel.

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 Android Security Patch Level
    Open Settings > About Phone > Security Patch Level, or run `getprop ro.build.version.security_patch` via ADB shell or terminal
    Affected if The security patch level is earlier than the month/year when this CVE was addressed in the Android Security Bulletin. Unpatched devices are affected.
  2. Verify kernel version
    Run `uname -a` or `cat /proc/version` in ADB shell or terminal to display the running kernel version
    Affected if The kernel version predates the patch date for this vulnerability. Compare against the kernel version in the Android Security Bulletin for the fixing patch level.
  3. Confirm kernel source patch status
    If you build your own kernel from source, check the kernel source code for the specific logic fix at the affected code locations referenced in the Android Security Bulletin
    Affected if The kernel source has not been updated to include the CVE fix commit.
  4. Check for CVE inclusion in device security bulletin
    Consult your device manufacturer's monthly security bulletin for the month this CVE was addressed
    Affected if Your device model has not received a security update that includes the fix for this kernel logic error.

A device is affected if it is running an unpatched Android version, indicated by a security patch level predating the CVE fix or a kernel version older than the patched version.

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 the affected code locations; given the kernel-level scope, this requires a system reboot to load the patched kernel.

Recommended fix Moderate confidence

Latest Android security patch level (monthly bulletin containing CVE-2024-34729 fix) or Android 15+ with latest kernel

  1. Check your device's Android Security Patch Level in Settings > About Phone > Android version (or similar, depending on device)
  2. If the patch level is older than the bulletin containing CVE-2024-34729, apply any available system updates
  3. For Android devices, ensure you have the latest monthly security update installed - go to Settings > System > Security update (or Settings > Software update)
  4. If no OTA update is available, consider upgrading to a newer Android version that includes the fix, or contact your device manufacturer for patch availability
Caveat Kernel-level security patches are generally backward-compatible; minimal risk of breaking changes from security-only patches

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

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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