Security readout for executives and security teams
Plain-English summary
This is a Qualcomm Snapdragon vulnerability affecting multiple chip families used in mobile, IoT, automotive, connectivity, compute, and audio products. A highly privileged local actor could trigger faulty queue-index handling through an IOCTL request and potentially alter memory. The main business concern is compromised devices where attackers already have elevated local access.
Executive priority
Treat this as a moderate-priority firmware and device-management issue. It is not described as remotely exploitable or actively exploited, but successful abuse could have high device impact. Prioritize high-value fleets and exposed operational technology using affected Snapdragon components.
Technical view
The flaw involves DCB/AVB algorithm processing of an invalid queue index supplied through an IOCTL request. Qualcomm describes the impact as arbitrary address modification. CVSS 3.1 is 6.7: local attack vector, low complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely in products incorporating the affected Qualcomm Snapdragon components listed by Qualcomm and CVE sources. Risk depends on whether the vulnerable firmware or driver path is present and reachable by a local highly privileged user. The source bundle does not identify internet-facing exposure.
Exploitation context
CISA KEV status is false, and the provided sources do not cite active exploitation or public exploit availability. The high privilege requirement lowers broad opportunistic risk, but device compromise impact could be severe after local privilege is obtained.
Researcher notes
The source bundle provides impact, CVSS, affected Qualcomm product families and chipset identifiers, but not a CWE, root-cause detail beyond invalid queue index handling, exploit indicators, or exact patch package names. Validation should stay tied to Qualcomm and OEM advisories rather than assumptions about downstream products.
Mitigation direction
- Review Qualcomm's May 2022 security bulletin for vendor guidance and affected chipset coverage.
- Obtain firmware or security updates from the device OEM or product vendor.
- Prioritize managed devices using affected Snapdragon mobile, IoT, automotive, compute, or connectivity components.
- Limit local administrative access on affected endpoints and embedded devices where possible.
- Track OEM advisories because Qualcomm component fixes may ship through device-specific updates.
Validation and detection
- Inventory devices and products containing the affected Qualcomm chipsets listed in the CVE record.
- Confirm current firmware, driver, and security patch levels against OEM and Qualcomm advisories.
- Check whether the relevant IOCTL-accessible component is present and enabled on deployed devices.
- Review EDR or device logs for suspicious privileged local activity on affected assets.
- Document unsupported or unpatchable devices for compensating controls or replacement planning.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2021-35092 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H0.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.7MediumVector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.qualcomm.com/company/product-security/bulletins/may-2022-bulletinCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.