LiveActive security incident?Get immediate response
CVE Record

CVE-2021-35087: Possible null pointer access due to improper validation of system information message to be processed in Sn...

Possible null pointer access due to improper validation of system information message to be processed in Snapdragon Industrial IOT, Snapdragon Mobile

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Qualcomm flaw can let a malformed system information message cause affected Snapdragon Mobile or Industrial IoT components to hit a null pointer condition. The documented impact is availability, not data theft or tampering. For executives, the business concern is device disruption across fleets that rely on listed Qualcomm chipsets.

Executive priority

Treat this as a high-priority firmware hygiene issue for affected fleets, especially operational IoT and business-critical mobile deployments. Urgency is driven by unauthenticated network attack characteristics and availability impact, not confirmed exploitation in the supplied sources.

Technical view

CVE-2021-35087 is an improper validation issue in processing system information messages. Qualcomm describes possible null pointer access in listed Snapdragon Mobile and Industrial IoT products. CVSS 3.1 is 7.5 with network attack vector, no privileges, no user interaction, and high availability impact only.

Likely exposure

Exposure is most likely in phones, IoT, or embedded products containing the listed Qualcomm components, including multiple Snapdragon, SDX, WCN, WCD, WSA, QCA, QCM, and QCS parts. Asset owners must map actual device hardware and firmware through OEM documentation.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates unauthenticated network reachability and low complexity, but the public bundle does not provide exploit details or real-world abuse reports.

Researcher notes

The source bundle does not name a CWE, affected firmware versions, proof-of-concept details, or product-specific fixes. Analysis should stay tied to Qualcomm's affected component list and CVSS vector. Avoid assuming every device using a Qualcomm component is vulnerable without OEM confirmation.

Mitigation direction

  • Review Qualcomm's May 2022 bulletin and relevant OEM advisories for CVE-2021-35087 coverage.
  • Prioritize firmware updates for devices using the listed Snapdragon Mobile or Industrial IoT components.
  • Apply vendor, carrier, or device-manufacturer updates through supported management channels.
  • If updates are unavailable, request written remediation guidance and affected-version confirmation from the OEM.
  • Track unsupported affected devices as availability risk until replacement or isolation is possible.

Validation and detection

  • Inventory devices and modules for the exact Qualcomm part numbers listed in the source bundle.
  • Confirm current firmware or build levels against Qualcomm and OEM security bulletin coverage.
  • Check mobile-device-management, carrier, or vendor portals for update deployment status.
  • Document devices with unknown chipsets as unresolved until vendor confirmation is obtained.
  • Monitor vendor advisories for any later exploitation or mitigation updates.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-35087 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-35087Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Qualcomm, Inc.Snapdragon Industrial IOT, Snapdragon MobileAR8035, QCA6390, QCA6391, QCA8081, QCA8337, QCM6490, QCS6490, SD 8 Gen1 5G, SD480, SD690 5G, SD695, SD765, SD765G, SD768G, SD778G, SD780G, SD865 5G, SD870, SD888 5G, SDX55, SDX55M, SDX65, SM7250P, WCD9341, WCD9370, WCD9375, WCD9380, WCD9385, WCN3988, WCN3991, WCN3998, WCN6740, WCN6750, WCN6850, WCN6851, WCN6855, WCN6856, WSA8810, WSA8815, WSA8830, WSA8835Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.