CVE-2024-45546
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 processing FIPS encryption or decryption IOCTL call invoked from user-space.
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 or driver handling FIPS encryption/decryption IOCTL requests, allowing a user-space application to trigger improper memory access during cryptographic 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 Qualcomm wireless/firmware componentsCheck system for Qualcomm Fastconnect, Wcd, Wsa, or Qcc hardware/driver modules. Use commands like 'lspci', 'lsusb', 'dmesg | grep -i qualcomm', or check /sys/firmware for embedded firmware versions.Affected if The system contains any of the affected Qualcomm components: Fastconnect 6900/7800, Qcc2073/2076, Sc8380xp, Wcd9380/9385, or Wsa8840.
-
Check Fastconnect firmware versionFor Fastconnect 6900/7800, check via 'cat /sys/class/net/*/device/firmware_version' or inspect wireless driver info with 'iw list' and look for firmware revision details.Affected if Fastconnect firmware is present (all versions of Fastconnect 6900 and 7800 are affected).
-
Check audio codec firmware versionsFor Wcd9380, Wcd9385, Wsa8840, check /proc/asound/card*/codec* or use 'cat /sys/bus/platform/drivers/*/firmware' to identify the codec firmware version.Affected if Wcd9380, Wcd9385, or Wsa8840 audio codec firmware is present (all versions are affected).
-
Check QCC Bluetooth audio firmwareFor Qcc2073/2076, check Bluetooth adapter firmware with 'btmgmt -i hci0 info' or inspect /lib/firmware/qca/ for downloaded firmware files.Affected if Qcc2073 or Qcc2076 Bluetooth audio firmware is present (all versions are affected).
-
Verify FIPS crypto IOCTL usageMonitor system for IOCTL calls related to FIPS encryption/decryption. Check if any application performs FIPS crypto operations via IOCTL to the affected kernel/driver. Review application logs or use strace on suspected applications.Affected if Applications are actively using FIPS encryption/decryption IOCTL requests with the affected Qualcomm firmware/driver.
A system is affected if it contains any Qualcomm Fastconnect 6900/7800, Qcc2073/2076, Sc8380xp, Wcd9380/9385, or Wsa8840 firmware AND actively uses FIPS cryptographic IOCTL operations through that firmware or driver.
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 for the affected kernel module or driver; if no patch available, consider disabling the affected FIPS crypto functionality or implementing additional input validation bounds checking on IOCTL parameters.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45546 — 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-45546 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