CVE-2020-11296
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 · uneditedArithmetic overflow can happen while processing NOA IE due to improper error handling in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon IoT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking
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 confidenceAn arithmetic overflow vulnerability exists in the processing of NOA (Notice of Absence) Information Elements within Qualcomm Snapdragon chipsets. The improper error handling during NOA IE processing can lead to integer overflow, potentially enabling remote attackers to cause denial of service or potentially execute arbitrary code via malformed network messages.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the Qualcomm Snapdragon chipset modelCheck your device specifications through Settings > About Phone, or use a system info app, or run 'getprop ro.product.board' or 'cat /proc/cpuinfo' in a terminal to find the processor identifierAffected if The chipset model matches any of these: Apq8009, Apq8017, Apq8053, Apq8064au, Apq8076, Apq8084, Apq8092, or Apq8094
-
Confirm the device uses a vulnerable chipset variantCross-reference the chipset identified in step 1 against the full list of affected product names provided in the CVE advisoryAffected if The exact chipset model is listed in the affected products list (all versions of the listed Apq models are affected)
-
Determine if the device processes NOA (Notice of Absence) Information ElementsThis vulnerability affects the modem/baseband firmware processing network messages. Check if your device connects to cellular networks (LTE/5G) where NOA IE messages are relevantAffected if The device has cellular connectivity and its modem/baseband processes NOA Information Elements from network signals
-
Check the modem/baseband firmware version if accessibleOn Android, try 'getprop gsm.version.baseband' or check Settings > About Phone > Baseband version. Compare against any available firmware update history from your device manufacturerAffected if The baseband/modem firmware is an older version and has not been patched through your OEM vendor
You are likely affected if your device uses any of the listed Qualcomm Snapdragon chipsets (Apq8009 through Apq8094) and connects to cellular networks, since all versions of these chipsets contain the vulnerability in NOA IE processing.
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 Qualcomm firmware/security updates for affected Snapdragon components through OEM vendor channels. Users should ensure their devices receive regular security patches from device manufacturers.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11296 — 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-2020-11296 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