CVE-2024-21460
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 · uneditedInformation disclosure when ASLR relocates the IMEM and Secure DDR portions as one chunk in virtual address 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 confidenceThis vulnerability allows information disclosure because Address Space Layout Randomization (ASLR) relocates the IMEM (Internal Memory) and Secure DDR (Secure Double Data Rate) regions as one contiguous chunk in virtual address space, rather than as independent random chunks. This enables attackers to potentially deduce memory layout and defeat ASLR protections.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
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 the chipset modelCheck the device or system information to determine if the chipset is one of the following: Fastconnect 6900, Fastconnect 7800, Qcm8550, Qcs8550, Sg8275p, Sm8550p, Snapdragon 8 Gen 2, or Snapdragon 8+ Gen 2Affected if The chipset matches any of the listed affected models
-
Confirm firmware versionAttempt to retrieve the firmware version from the device or system logs, typically accessible via diagnostic tools or by checking the wireless/wireless firmware subsystemAffected if The firmware version cannot be determined or is present on an affected chipset (all versions are affected)
-
Inspect IMEM and Secure DDR memory layoutAnalyze the virtual memory mapping of the firmware, specifically examining the relative positions of IMEM (Internal Memory) and Secure DDR regions in the address spaceAffected if IMEM and Secure DDR regions appear as a single contiguous block rather than independently randomized separate chunks
If the device uses any of the listed Qualcomm chipsets with their firmware, the ASLR implementation is vulnerable because IMEM and Secure DDR are randomized as one contiguous chunk instead of independent chunks.
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.
dbcve · scopedThis requires a firmware update from the device vendor that modifies the ASLR implementation to randomize IMEM and Secure DDR as separate, independently relocated chunks in virtual address space.
Firmware version containing CVE-2024-21460 fix (check Qualcomm security bulletin for specific release)
- Check Qualcomm's security bulletins (docs.qualcomm.com) for CVE-2024-21460 to identify the specific firmware version containing the security fix
- Contact your device/original equipment manufacturer (OEM) to obtain the updated firmware that addresses this vulnerability
- Apply the firmware update following the OEM's standard update procedure
- Verify the ASLR implementation now properly randomizes IMEM and Secure DDR as separate chunks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation16.0 h
- Testing10.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 $10,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21460 — 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-21460 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