dbcve.org
AndroidOperating system · Google

CVE-2024-32895

HIGH · 7.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 →
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 BCMFASTPATH of dhd_msgbuf.c, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege 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 BCMFASTPATH component of the Broadcom WiFi driver (dhd_msgbuf.c). The issue stems from a missing bounds check before a write operation, allowing an out-of-bounds write that can be exploited for local privilege escalation without requiring user interaction or additional execution privileges.

MitigationApply the vendor-supplied patch for CVE-2024-32895 to the affected Broadcom wireless driver. If no patch is available, consider updating to a newer driver version that includes the bounds-checking fix.

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. Confirm Android OS is running
    Check /system/build.prop for 'ro.build.version.sdk' or run 'getprop ro.build.version.release'
    Affected if Device is not running Android (not affected in non-Android environments)
  2. Identify Broadcom WiFi driver presence
    Check /proc/modules for 'dhd' or 'bcmdhd' entries, or inspect 'getprop | grep wlan' output
    Affected if No Broadcom WiFi driver modules are loaded (driver not present)
  3. Check WiFi driver version
    Run 'getprop ro.bt.bdaddr_path' or check /sys/class/net/wlan0/device/uevent for BCM chip identification; also check 'getprop' for 'wlan.driver' properties
    Affected if Driver version cannot be determined or shows unpatched BCM driver (vulnerable)
  4. Verify dhd_msgbuf component is in use
    Check 'ls -la /sys/module/dhd/' or 'cat /proc/modules | grep dhd_msgbuf' on the device
    Affected if The dhd_msgbuf component is not loaded or not present (vulnerability not reachable)
  5. Check for kernel symbols related to dhd_msgbuf
    If available, check /proc/kallsyms for 'dhd_msgbuf' related functions to confirm the driver component is active
    Affected if The vulnerable driver component is not active in the kernel (may indicate already patched or different driver)

If the device runs Android with an active Broadcom WiFi driver (dhd/bcmdhd) containing the dhd_msgbuf component, the environment is likely affected since all Android versions using this driver are vulnerable until the vendor patch is applied.

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 patch for CVE-2024-32895 to the affected Broadcom wireless driver. If no patch is available, consider updating to a newer driver version that includes the bounds-checking fix.

Recommended fix Moderate confidence

Android security patch level as specified in the relevant Android Security Bulletin (check source.android.com for the specific bulletin containing this CVE fix)

  1. 1. Check the Android Security Bulletin for the month this CVE was addressed to identify the specific patch level containing the fix
  2. 2. Update your Android device to a system software version that includes the security patch level addressing CVE-2024-32895
  3. 3. Verify the update was applied successfully by checking Settings > About Phone > Security Patch Level
Caveat Security updates may have minimal compatibility impact; ensure backup of data before applying major updates

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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