CVE-2024-23379
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 while unmapping the fastrpc map when two threads can free the same map in concurrent scenario.
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 in the fastrpc kernel driver allows two concurrent threads to free the same memory map during unmapping, resulting in a double-free that causes memory corruption. The vulnerability stems from insufficient synchronization when multiple threads attempt to simultaneously unmap the same fastrpc map.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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 Qualcomm audio/coexistence chip presenceList hardware devices or use lspci/mmc/i2c tools to enumerate onboard Qualcomm chips. Look for WSA (audio amplifier), WCD (codec), or WCN (connectivity) components in the device tree or hardware inventory.Affected if Any of these chips are present: Wsa8835, Wsa8830, Wsa8815, Wsa8810, Wcn3990, Wcd9380, Wcd9341, Wcd9340
-
Determine firmware version of affected chipQuery the firmware version through vendor-specific tools (e.g., audio firmware loader, ethtool for WCN, or manufacturer diagnostic interface) or read from /sys/firmware or device-specific debug interfaces.Affected if Firmware version cannot be determined or matches any version (all versions of listed chips are affected)
-
Verify fastrpc driver is loadedCheck if the fastrpc kernel module is loaded by running 'lsmod | grep fastrpc' or checking /proc/modules. Also verify /dev/fastrpc or similar device nodes exist.Affected if The fastrpc driver is loaded and the associated device interface is present
-
Check for concurrent fastrpc map operationsReview kernel logs (dmesg, /var/log/kern.log) for any crash traces, memory corruption reports, or double-free errors related to fastrpc. Also check for 'fastrpc' in kernel panic logs.Affected if Any kernel crashes, memory corruption, or double-free errors referencing fastrpc are found in logs
If any affected Qualcomm chip (Wsa8835, Wsa8830, Wsa8815, Wsa8810, Wcn3990, Wcd9380, Wcd9341, Wcd9340) is present with fastrpc driver active, the environment is vulnerable since all firmware versions are affected.
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 (e.g., mutex lock or reference counting) around the map unmap/free operation in the fastrpc driver to prevent concurrent access to the same map structure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23379 — 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-23379 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