dbcve.org
AndroidOperating system · Google

CVE-2024-29786

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 pktproc_fill_data_addr_without_bm of link_rx_pktproc.c, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution 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 buffer overflow vulnerability exists in the pktproc_fill_data_addr_without_bm function within link_rx_pktproc.c. The function fails to validate buffer bounds before writing packet data, allowing an attacker to write beyond allocated memory boundaries. This enables remote code execution without requiring any privileges or user interaction.

MitigationImplement proper bounds checking in pktproc_fill_data_addr_without_bm to validate buffer limits before memory writes. Apply vendor-provided patches immediately as this is a critical RCE vulnerability.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 version
    Go to Settings > About Phone > Android version to determine the installed OS version
    Affected if Any Android version is running, as all versions are affected according to the CVE data
  2. Verify patch level
    Go to Settings > About Phone > Security Patch Level to check the installed security update
    Affected if The Security Patch Level is earlier than the Google Android security bulletin that addressed CVE-2024-29786
  3. Identify vulnerable component
    Examine if the device uses the link_rx_pktproc.c packet processing module in its baseband or network driver - this typically requires access to device firmware or kernel logs
    Affected if The device contains the pktproc_fill_data_addr_without_bm function in its network packet processing code and the function lacks bounds checking as described in the CVE
  4. Confirm exploitability conditions
    Review network traffic handling - the vulnerability triggers when the pktproc_fill_data_addr_without_bm function processes inbound packet data without proper buffer boundary validation
    Affected if Packet processing with the vulnerable function is active and receives untrusted network input

If the device runs any version of Android and lacks the specific security patch for CVE-2024-29786, the environment is affected by this buffer overflow vulnerability in the packet processing module.

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

Implement proper bounds checking in pktproc_fill_data_addr_without_bm to validate buffer limits before memory writes. Apply vendor-provided patches immediately as this is a critical RCE vulnerability.

Recommended fix Moderate confidence

Apply the Android security patch level that addresses CVE-2024-29786 (refer to Android Security Bulletin)

  1. Check the Android Security Bulletin for CVE-2024-29786 at source.android.com/security/bulletin for the specific Android version that contains the fix
  2. Apply the latest Android security patch level available for your device
  3. If no patch is available from your device manufacturer, consider upgrading to a device that receives regular security updates
  4. For Android devices, ensure Google Play system updates are installed

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
  • Testing16.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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