CVE-2025-47356
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 concurrently access and modify shared resources.
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 confidenceMemory corruption vulnerability caused by race conditions when multiple threads concurrently access and modify shared resources without proper synchronization. The lack of thread-safe mechanisms (such as mutexes, locks, or atomic operations) leads to undefined behavior and potential exploitation via crafted concurrent access patterns.
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 installed Qualcomm firmware componentsOn Linux, run 'ls /lib/firmware/qcom/' or check 'dmesg' for firmware loading messages. On Windows, check Device Manager for Qualcomm device details or use 'systeminfo' and driver queries.Affected if Any of the following firmware modules are present: Cologne, Fastconnect 6900, Fastconnect 7800, Qca0000, Sc8380xp, Wcd9378c, Wcd9380, or Wcd9385
-
Check Qualcomm audio/wireless driver versionOn Linux, run 'modinfo <module_name>' for modules like ath11k, wcd938x, or qca6390. On Windows, right-click the device in Device Manager, select Properties, and check the Driver version field.Affected if The driver or firmware corresponds to any of the affected Qualcomm components listed in the CVE
-
Verify concurrent access capabilityReview application and system configuration to determine if multiple threads can simultaneously invoke functions provided by the affected Qualcomm firmware components (e.g., concurrent WiFi operations, audio codec access).Affected if Multiple threads or processes can concurrently access the Qualcomm firmware interfaces without explicit synchronization protection
A system is affected if it contains any of the listed Qualcomm firmware components (Cologne, Fastconnect 6900/7800, Qca0000, Sc8380xp, Wcd9378c, Wcd9380, or Wcd9385) and those components can be accessed concurrently by multiple threads.
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 synchronization primitives (e.g., mutexes, locks, semaphores) around all access and modification paths to shared resources, or refactor code to eliminate shared mutable state through thread-local storage or immutable data structures.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47356 — 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-47356 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