dbcve.org
AndroidOperating system · Google

CVE-2024-32925

HIGH · 8.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 →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 dhd_prot_txstatus_process of dhd_msgbuf.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 missing bounds check in dhd_prot_txstatus_process within the Broadcom wireless driver (dhd_msgbuf.c) allows an out-of-bounds write when processing TX status messages. This can be exploited remotely for code execution without any user interaction or privileges, making it highly severe.

MitigationApply vendor firmware/driver updates from the device manufacturer or Broadcom to patch the bounds check vulnerability in the wireless driver.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Broadcom wireless driver presence
    Check if the device uses Broadcom WiFi chipset by examining /proc/kallsyms or kernel modules for 'dhd' or 'bcmdhd' entries, or check hardware info via 'getprop' for wifi chip vendor
    Affected if The device has Broadcom wireless driver loaded (dhd, bcmdhd, or wl module present)
  2. Locate the vulnerable driver file
    Search for dhd_msgbuf.c or the compiled driver module (dhd.ko, bcmdhd.ko, or wl.ko) in /system/lib/modules/ or /lib/modules/
    Affected if The Broadcom dhd driver file exists on the device
  3. Confirm the vulnerable function exists
    Examine the driver binary or source for the function dhd_prot_txstatus_process - this can be done via 'grep' if source/module is accessible, or by checking kernel symbols
    Affected if The function dhd_prot_txstatus_process is present in the loaded driver
  4. Determine if bounds check is missing (requires code review)
    If driver source or disassembly is accessible, verify whether dhd_prot_txstatus_process contains proper array bounds checking before TX status processing operations
    Affected if The function lacks proper bounds validation before processing TX status messages

The device is affected if it runs Android with a Broadcom wireless driver containing the dhd_prot_txstatus_process function, since all Android versions with this driver are vulnerable to the missing bounds check.

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 firmware/driver updates from the device manufacturer or Broadcom to patch the bounds check vulnerability in the wireless driver.

Recommended fix Moderate confidence

The fix is delivered through Android Security Patch Levels. Specific release varies; check the Android Security Bulletin for CVE-2024-32925 to identify the exact Security Patch Level that contains the fix.

  1. Check the Android Security Bulletin for the month this CVE was patched (refer to source.android.com/security/bulletin)
  2. Apply the latest Android system update on the affected device
  3. For device manufacturers: integrate the security patch level that includes the fix for dhd_prot_txstatus_process in dhd_msgbuf.c
  4. Verify the patch was applied by confirming the device shows the corresponding Android Security Patch Level in Settings > About Phone > Android version
Caveat None expected; this is a security fix within an existing driver component.

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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