dbcve.org
AndroidOperating system · Google

CVE-2024-32913

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 wl_notify_rx_mgmt_frame of wl_cfg80211.c, there is a possible out of bounds write due to an integer overflow. 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 · moderate confidence

A buffer overflow vulnerability exists in the wl_notify_rx_mgmt_frame function within the wl_cfg80211.c wireless driver, where an integer overflow allows an out-of-bounds write operation when processing management frames. This enables remote code execution without requiring any privileges or user interaction, likely making it exploitable by adjacent network attackers.

MitigationApply the latest vendor firmware/driver update that addresses the integer overflow vulnerability in wl_notify_rx_mgmt_frame, or implement proper bounds validation before memory allocation and write operations in the affected function.

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. Identify Android build and kernel version
    Run 'getprop ro.build.version.release' and 'uname -a' to obtain the Android version and kernel version
    Affected if The device runs any Android version as all versions are affected per the advisory
  2. Check for presence of the vulnerable wl_cfg80211 driver
    Examine /system/lib/modules or /vendor/lib/modules for files named wl_cfg80211.ko or similar Broadcom wireless driver modules using 'find / -name wl_cfg80211* 2>/dev/null'
    Affected if The wl_cfg80211 wireless driver module is present on the device
  3. Verify wireless interface is active
    Run 'ip link show' or 'iwconfig' to list network interfaces and determine if a wireless interface (e.g., wlan0) exists and is up
    Affected if A wireless interface managed by the vulnerable driver is present and enabled, as the flaw triggers during management frame processing
  4. Confirm driver is handling management frames
    Check kernel logs with 'dmesg | grep -i wl' or 'logcat | grep -i wl_cfg80211' for management frame reception activity
    Affected if The device is actively processing wireless management frames through the affected function, which is required for exploitation

The device is affected if it runs any Android version and contains the wl_cfg80211 wireless driver with an active wireless interface handling management frames.

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 latest vendor firmware/driver update that addresses the integer overflow vulnerability in wl_notify_rx_mgmt_frame, or implement proper bounds validation before memory allocation and write operations in the affected function.

Recommended fix Moderate confidence
  1. Contact your device OEM (manufacturer) to request the Android security patch that addresses CVE-2024-32913
  2. Verify with your OEM that the patch includes the fix for the integer overflow in wl_notify_rx_mgmt_frame in wl_cfg80211.c
  3. Apply the OEM-supplied firmware/security update to your Android device
  4. If you are an OEM or chipset integrator, obtain the patched wl_cfg80211.c from Broadcom (the chipset vendor) and integrate it into your kernel driver stack
  5. Rebuild and deploy the updated firmware images to affected devices
Caveat Security patches for driver-level vulnerabilities typically do not introduce breaking changes but must be validated by the device OEM for hardware compatibility

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

Fix this in Android Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA8.0 h
34.0 hours of engineering $5,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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