CVE-2024-47038
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 · uneditedIn dhd_prot_flowrings_pool_release of dhd_msgbuf.c, there is a possible outcof bounds write due to a missing bounds check. This could lead to localcescalation of privilege with no additional execution privileges needed. Usercinteraction 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 confidenceA missing bounds check in the dhd_prot_flowrings_pool_release function in dhd_msgbuf.c allows an out-of-bounds write to kernel memory. This memory corruption vulnerability in the WiFi driver (dhd) can be exploited locally to escalate privileges to root without requiring additional execution privileges or user interaction.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device runs AndroidCheck /system/build.prop for ro.build.id or run 'getprop ro.build.version.sdk' to verify the OS is AndroidAffected if The device is running any Android version (all versions are affected per the CVE)
-
Verify dhd WiFi driver presenceCheck if the dhd kernel module is loaded by examining /proc/modules or running 'lsmod | grep dhd'Affected if The dhd module is loaded, indicating this WiFi driver component is present in the system
-
Check dhd driver versionExamine /sys/module/dhd/version or /sys/class/net/wlan0/device/driver_version if available, or check kernel config for CONFIG_BCM optionsAffected if A dhd driver version exists (even if version cannot be determined, the driver presence indicates the vulnerable component is in use)
-
Verify WiFi interface is activeCheck for wireless interface presence via 'ip link show' or 'ifconfig -a' looking for wlan0Affected if A WiFi interface (wlan0) exists, confirming the dhd driver is managing a WiFi device and the vulnerable code path could be triggered
If the device runs Android with the dhd WiFi driver module loaded and managing a WiFi interface, the environment is affected by this vulnerability and requires a vendor-supplied kernel/driver patch to remediate.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the vendor-supplied driver/firmware patch that adds proper bounds validation before writing to the flow ring pool buffer. This is a kernel-space driver vulnerability requiring a kernel/driver update rather than an application-level fix.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47038 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47038 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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