CVE-2025-47359
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 · uneditedMemory Corruption when multiple threads simultaneously access a memory free API.
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 confidenceA race condition vulnerability exists where multiple threads can simultaneously access a memory deallocation API, leading to memory corruption. This is likely a double-free or use-after-free condition that occurs when proper thread synchronization is missing around memory free operations.
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 versionsall versionsall versionsall versionsall versionsall versionsall versionsall 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.
-
Identify if your device uses an affected Qualcomm chipCheck your device documentation, hardware specifications, or system logs for the wireless chipset model. Look for: Qca6391, Qca6420, Qca6430, Qcc2072, Sc8380xp, Sc8180x Ad, Sc8180xp Ad, or Sc8180x AaabAffected if Your device or network hardware contains any of these Qualcomm chip identifiers in its specifications or running configuration
-
Determine the firmware version of the Qualcomm componentAccess your device's admin interface, system information page, or run diagnostic commands such as 'lspci -v', 'iw list', 'cat /proc/version', or vendor-specific commands to retrieve the installed firmware versionAffected if Any firmware version is returned for the affected chip families - all versions are vulnerable
-
Verify the wireless or connectivity subsystem is activeCheck if the wireless interface is up and running using commands like 'ip link show', 'iw dev', 'ifconfig', or through the device management interfaceAffected if The affected Qualcomm firmware is actively loaded and running on your system
-
Confirm multi-threaded operation contextReview system logs, driver information, or vendor documentation to verify the firmware handles concurrent operations - this is typically inherent to Wi-Fi/Bluetooth firmware handling multiple clientsAffected if The device handles any concurrent wireless connections or multi-client operations, which triggers the vulnerable code path
If your device or network hardware runs any firmware version on the listed Qualcomm chip models (Qca6391, Qca6420, Qca6430, Qcc2072, Sc8380xp, Sc8180x Ad, Sc8180xp Ad, Sc8180x Aaab) and utilizes multi-threaded operations, you are affected by this race condition vulnerability.
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 dataImplement proper mutex/lock protection around all memory free operations and review code paths for potential race conditions in multi-threaded contexts.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47359 — 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-2025-47359 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