CVE-2024-21465
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 key blob passed by the user.
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 memory corruption vulnerability exists in the processing of user-supplied key blobs. When malformed or malicious key blob data is passed to the affected component, improper handling leads to memory corruption that could allow an attacker to execute arbitrary code or cause a denial of service.
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 modem firmware versionAccess the modem/Baseband processor interface via AT commands (e.g., ATI, AT+CGMR) or through the device's firmware management interface to retrieve the Qualcomm 9205 LTE Modem Firmware versionAffected if The device runs Qualcomm 9205 LTE Modem Firmware of any version
-
Identify Qualcomm FastConnect adapter firmwareUse system utilities (such as 'lspci', 'lsusb', or vendor-specific tools like 'iw list', ' Qualcomm Flash Tool') to enumerate wireless adapters and retrieve the Fastconnect 6200 or 6700 firmware versionAffected if The system contains a Qualcomm FastConnect 6200 or 6700 wireless adapter with any firmware version installed
-
Identify Qualcomm audio codec firmwareQuery the audio subsystem or use vendor tools to retrieve the CSRA6620 or CSRA6640 firmware version from the deviceAffected if The device uses Qualcomm CSRA6620 or CSRA6640 audio codec firmware of any version
-
Identify Qualcomm Ethernet PHY firmwareAccess the network interface or use PHY management tools (such as 'ethtool', 'phytool', or vendor-specific configuration utilities) to query the Ar8031 or Ar8035 Ethernet PHY firmware versionAffected if The network device implements a Qualcomm Ar8031 or Ar8035 Ethernet PHY with any firmware version
-
Identify Qualcomm Aqt1000 firmwareCheck the device management interface or firmware inventory for presence of the Qualcomm Aqt1000 component and retrieve its firmware versionAffected if The system includes a Qualcomm Aqt1000 component with any firmware version present
-
Check for key blob processing activityReview system logs, crash dumps, and security monitoring tools for memory corruption indicators (crashes, abnormal memory access errors) related to key blob handling in Qualcomm firmware componentsAffected if Key blob processing is actively used and memory corruption events are observed in logs
A system is affected if any of the listed Qualcomm firmware components (9205 LTE Modem, FastConnect 6200/6700, CSRA6620/6640, Ar8031/8035, Aqt1000) are present, since all versions are vulnerable when key blob input is processed.
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-supplied patches when available. Until a patch is released, restrict access to affected components and validate all key blob input before processing.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21465 — 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-21465 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