CVE-2021-35087
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 · uneditedPossible null pointer access due to improper validation of system information message to be processed in 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 · moderate confidenceA null pointer access vulnerability exists in Snapdragon Industrial IOT and Snapdragon Mobile chipsets due to improper validation of system information messages being processed. An attacker could exploit this by sending specially crafted messages to trigger the null pointer dereference, potentially causing denial of service or code execution.
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 or firmware in useRun commands such as 'lspci', 'lsusb', 'dmesg', or check the device/system documentation to identify the specific Qualcomm component (Ar8035, Qca6390, Qca6391, Qca8081, Qca8337, Qcm6490, Qcs6490, or Sd 8 Gen1 5g).Affected if The device uses any of the following: Ar8035, Qca6390, Qca6391, Qca8081, Qca8337, Qcm6490, Qcs6490, or Sd 8 Gen1 5g firmware.
-
Verify the firmware versionQuery the firmware version through vendor-specific tools, device management interfaces, or by inspecting /proc or /sys filesystem entries for the network controller or wireless card firmware version.Affected if All versions of the listed firmware are affected, so any version confirms exposure.
-
Determine if the system processes network system information messagesIdentify if the Qualcomm component handles wireless or network communication that processes system information messages (such as beacon frames, probe requests, or management frames in Wi-Fi/Bluetooth contexts). Check network interface configuration and active services.Affected if The vulnerable firmware is actively processing wireless or network communications.
-
Assess network exposure of the Qualcomm componentReview firewall rules, network segmentation, and access controls to determine if untrusted network actors can send packets to the affected chipset. Check if the device is directly accessible from untrusted networks.Affected if The device with affected firmware is accessible from network segments where attackers could send specially crafted messages.
The environment is affected if it deploys any of the listed Qualcomm firmware components (Ar8035, Qca6390, Qca6391, Qca8081, Qca8337, Qcm6490, Qcs6490, or Sd 8 Gen1 5g) and those components process network traffic from potentially untrusted sources.
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 vendor firmware/security updates for affected Snapdragon chipsets. If patches are unavailable, restrict network exposure and monitor for exploitation attempts.
- 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-2021-35087 — 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-2021-35087 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