LiveActive security incident?Get immediate response
CVE Record

CVE-2021-35082: Improper integrity check can lead to race condition between tasks PDCP and RRC?

Improper integrity check can lead to race condition between tasks PDCP and RRC? right after a valid RRC security mode command packet has been received in Snapdragon Industrial IOT

CriticalCVSS 9.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This is a critical Qualcomm vulnerability affecting specific Snapdragon Industrial IoT components. The reported issue could let a network-adjacent attacker influence confidentiality and integrity after a valid RRC security mode command is received. Availability impact is not listed. The public record is terse, so operational risk depends on whether affected chipsets are present in deployed devices.

Executive priority

Treat this as high-priority asset validation and vendor follow-up for industrial IoT fleets. The severity is critical, but the evidence provided does not establish active exploitation. Business urgency is greatest where affected modules support operational technology, remote telemetry, or field equipment with limited patch windows.

Technical view

CVE-2021-35082 is an improper integrity check in Snapdragon Industrial IoT involving a race condition between PDCP and RRC tasks after receipt of a valid RRC security mode command packet. CVSS 3.1 is 9.1: network attack vector, low complexity, no privileges, no user interaction, high confidentiality and integrity impact, no availability impact.

Likely exposure

Exposure is limited to products using Qualcomm Snapdragon Industrial IoT components listed in the CVE: MDM9206, QCA9367, and QCA9377. Organizations should check embedded-device BOMs, cellular or industrial IoT modules, and OEM firmware advisories rather than assuming all Qualcomm devices are affected.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not listed as KEV. The scoring indicates remotely reachable conditions with no privileges or user interaction, but public exploit details and reliable detection indicators are not provided in the source bundle.

Researcher notes

The record lacks CWE mapping, patch identifiers, exploit indicators, and detailed affected firmware ranges. Analysis should stay bounded to Qualcomm’s listed products and OEM implementations. The key research questions are chipset presence, firmware lineage, and whether the OEM integrated Qualcomm’s May 2022 remediation guidance.

Mitigation direction

  • Identify devices using MDM9206, QCA9367, or QCA9377 components.
  • Review Qualcomm May 2022 bulletin and OEM advisories for official fixes.
  • Apply vendor-approved firmware or baseband updates when available.
  • Prioritize devices exposed through cellular or industrial wireless networks.
  • Use network segmentation and monitoring while awaiting OEM remediation.

Validation and detection

  • Map device inventory to chipset and firmware versions.
  • Confirm whether each OEM product uses affected Qualcomm components.
  • Check vendor advisories against CVE-2021-35082 and May 2022 bulletin references.
  • Verify deployed firmware matches vendor-remediated releases, if published.
  • Document unresolved devices requiring OEM confirmation.
Prepared
Confidence
medium
Sources
3

Public sources used

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-35082 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
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

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

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
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2021-35082Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Qualcomm, Inc.Snapdragon Industrial IOTMDM9206, QCA9367, QCA9377Listed
Weakness

CWE details

No CWE listed

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