CVE-2021-35108: Improper checking of AP-S lock bit while verifying the secure resource group permissions can lead to non secure read and write access in Sna
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Improper checking of AP-S lock bit while verifying the secure resource group permissions can lead to non secure read and write access in Snapdragon Connectivity, Snapdragon Mobile
- Published
- Sep 2, 2022
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- CWE-754
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- 6.8
- CNA · qualcomm
- 6.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| qualcomm | sd 8 gen1 5g firmware | cpe:2.3:o:qualcomm:sd_8_gen1_5g_firmware |
| qualcomm | sm8475 | cpe:2.3:h:qualcomm:sm8475 |
| qualcomm | sm7450 firmware | cpe:2.3:o:qualcomm:sm7450_firmware |
| qualcomm | sm7450 | cpe:2.3:h:qualcomm:sm7450 |
| qualcomm | sm8475 firmware | cpe:2.3:o:qualcomm:sm8475_firmware |
| qualcomm | sm8475p firmware | cpe:2.3:o:qualcomm:sm8475p_firmware |
| qualcomm | sm8475p | cpe:2.3:h:qualcomm:sm8475p |
| qualcomm | wcd9370 firmware | cpe:2.3:o:qualcomm:wcd9370_firmware |
| qualcomm | wcd9370 | cpe:2.3:h:qualcomm:wcd9370 |
| qualcomm | wcd9375 firmware | cpe:2.3:o:qualcomm:wcd9375_firmware |
| qualcomm | wcd9375 | cpe:2.3:h:qualcomm:wcd9375 |
| qualcomm | wcd9380 firmware | cpe:2.3:o:qualcomm:wcd9380_firmware |
and 17 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm sd 8 gen1 5g firmwareall versions
- qualcomm sm7450 firmwareall versions
- qualcomm sm8475 firmwareall versions
- qualcomm sm8475p firmwareall versions
- qualcomm wcd9370 firmwareall versions
- qualcomm wcd9375 firmwareall versions
- qualcomm wcd9380 firmwareall versions
- qualcomm wcd9385 firmwareall versions
- qualcomm wcn6750 firmwareall versions
- qualcomm wcn6855 firmwareall versions
- qualcomm wcn6856 firmwareall versions
- qualcomm wcn7851 firmwareall versions
- qualcomm wsa8830 firmwareall versions
- qualcomm wsa8832 firmwareall versions
- qualcomm wsa8835 firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (qualcomm). Independent of NVD's CPE analysis and usually ahead of it.
Qualcomm, Inc. Snapdragon Connectivity, Snapdragon Mobile
- SD 8 Gen1 5G, SM7450, SM8475, SM8475P, WCD9370, WCD9375, WCD9380, WCD9385, WCN6750, WCN6855, WCN6856, WCN7851, WSA8830, WSA8832, WSA8835affected
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-25708Memory corruption in WLAN due to buffer copy without checking size of input while parsing keys in Snapdragon Connectivity, Snapdragon Mobile39Monitor
- CVE-2021-35110Possible buffer overflow to improper validation of hash segment of file while allocating memory in Snapdragon Connectivity, Snapdragon Mobil35Monitor
- CVE-2022-40540Buffer copy without checking the size of input in Linux Kernel31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-35091Jun 14, 2022 · Possible out of bounds read due to improper typecasting while handling page fault for global memory in Snapdragon Connectivity, Snapdragon M31Monitor
- ← EarlierCVE-2022-22090Jun 14, 2022 · Memory corruption in audio due to use after free while managing buffers from internal cache in Snapdragon Compute, Snapdragon Connectivity, 31Monitor
- Later →CVE-2021-35109Sep 2, 2022 · Possible address manipulation from APP-NS while APP-S is configuring an RG where it tries to merge the address ranges in Snapdragon Connecti27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-754 · Improper Check for Unusual or Exceptional ConditionsCVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.