CVE-2020-11200
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 · uneditedBuffer over-read while parsing RPS due to lack of check of input validation on values received from user side. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile
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 · high confidenceA buffer over-read vulnerability exists in the RPS parsing functionality of Qualcomm Snapdragon chipsets due to insufficient input validation on user-supplied values. The lack of bounds checking allows an attacker to read beyond buffer boundaries by providing malformed RPS data.
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 chipset modelQuery system hardware information to determine the exact chipset (check via 'lspci', 'lsusb', '/proc/cpuinfo', device tree files, or system hardware databases). The specific chipset model must be identified from the affected list.Affected if The chipset model matches Apq8053, Apq8064au, Apq8096au, Aqt1000, Ar8151, Mdm9640, Mdm9650, or Msm8953 from the affected products list
-
Confirm RPS parsing functionality is in useDetermine if the system utilizes Receive Packet Steering (RPS) for network packet distribution. Check sysfs entries such as '/sys/class/net/*/queues/rx-*/rps_cpus' or review network driver configuration to see if RPS is enabled.Affected if RPS is enabled and the system processes network packets using RPS on the affected hardware
-
Inspect RPS input handlingExamine the network driver or firmware code that handles RPS data parsing. Look for the code path that processes RPS configuration data and validates input length and values before buffer access.Affected if The RPS parsing implementation lacks proper bounds checking on RPS data before buffer access operations
If the system contains any of the listed Qualcomm chipsets (Apq8053, Apq8064au, Apq8096au, Aqt1000, Ar8151, Mdm9640, Mdm9650, Msm8953) and processes RPS data without adequate input validation, it is vulnerable to CVE-2020-11200.
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 dataImplement strict input validation and bounds checking on all RPS parsing code paths to verify data length and value ranges before buffer access operations.
- Consultation6.0 h
- Implementation8.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 $8,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11200 — 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-11200 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