CVE-2024-49840
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 Invoking IOCTL calls from user-space to validate FIPS encryption or decryption functionality.
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 in the kernel/driver IOCTL handler for FIPS encryption/decryption validation. User-space applications can trigger improper memory operations when invoking IOCTL calls to validate cryptographic functionality, potentially leading to privilege escalation or system instability.
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 Qualcomm firmware componentsRun 'ls /lib/firmware/qcom/' or check system firmware directories for presence of fastconnect, qcc, sc8380xp, wcd938x, or wsa8840 firmware filesAffected if Any of the listed Qualcomm firmware components (Fastconnect 6900/7800, Qcc2073/2076, Sc8380xp, Wcd9380/9385, Wsa8840) are present on the system
-
Check firmware version informationRetrieve firmware version details using 'cat /sys/class/firmware/*/version' or inspect firmware file metadata, or query the wireless driver for firmware version via 'iw dev' or 'wpa_cli -i wlan0 status'Affected if The installed firmware version matches any of the affected products (all versions of Fastconnect 6900/7800, Qcc2073/2076, Sc8380xp, Wcd9380/9385, Wsa8840)
-
Verify FIPS cryptographic validation is accessibleCheck if IOCTL interfaces for FIPS encryption/decryption validation are exposed by querying system IOCTL listings or examining driver configuration, look for FIPS-related IOCTL calls in driver debug outputs or system call tracesAffected if The system has FIPS IOCTL handler functionality exposed through the kernel/driver interface for the affected Qualcomm components
-
Monitor for anomalous IOCTL activityUse tools like 'auditctl' to log IOCTL system calls targeting the Qualcomm driver, or capture network/wireless driver traffic for unexpected FIPS validation requestsAffected if IOCTL calls to FIPS encryption/decryption validation handlers show unusual patterns or originate from untrusted user-space processes
If the system has any of the listed Qualcomm firmware components (Fastconnect 6900/7800, Qcc2073/2076, Sc8380xp, Wcd9380/9385, Wsa8840) with FIPS IOCTL functionality enabled and accessible to user-space, the environment is likely affected by this 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 dataApply vendor-provided security patches or firmware updates to the affected kernel/driver component that addresses the memory corruption vulnerability in the FIPS IOCTL handling code path.
- Consultation8.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 $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49840 — 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-49840 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