CVE-2021-1960: Improper handling of ASB-C broadcast packets with crafted opcode in LMP can lead to uncontrolled resource consumption in Snapdragon Auto, Sn
Noroxi assessment
Priority: Monitor (action score 26/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.23% (FIRST EPSS).
- Someone on the same network segment can trigger it. 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.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
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 handling of ASB-C broadcast packets with crafted opcode in LMP can lead to uncontrolled resource consumption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wired Infrastructure and Networking
- Published
- Sep 9, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-20
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 6.5
- CNA · qualcomm
- 6.5
- 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 | qcn7606 | cpe:2.3:h:qualcomm:qcn7606 |
| qualcomm | aqt1000 firmware | cpe:2.3:o:qualcomm:aqt1000_firmware |
| qualcomm | aqt1000 | cpe:2.3:h:qualcomm:aqt1000 |
| qualcomm | ar8031 firmware | cpe:2.3:o:qualcomm:ar8031_firmware |
| qualcomm | ar8031 | cpe:2.3:h:qualcomm:ar8031 |
| qualcomm | ar8035 firmware | cpe:2.3:o:qualcomm:ar8035_firmware |
| qualcomm | ar8035 | cpe:2.3:h:qualcomm:ar8035 |
| qualcomm | csra6620 firmware | cpe:2.3:o:qualcomm:csra6620_firmware |
| qualcomm | csra6620 | cpe:2.3:h:qualcomm:csra6620 |
| qualcomm | csra6640 firmware | cpe:2.3:o:qualcomm:csra6640_firmware |
| qualcomm | csra6640 | cpe:2.3:h:qualcomm:csra6640 |
| qualcomm | csrb31024 firmware | cpe:2.3:o:qualcomm:csrb31024_firmware |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm aqt1000 firmwareall versions
- qualcomm ar8031 firmwareall versions
- qualcomm ar8035 firmwareall versions
- qualcomm csra6620 firmwareall versions
- qualcomm csra6640 firmwareall versions
- qualcomm csrb31024 firmwareall versions
- qualcomm ipq5010 firmwareall versions
- qualcomm ipq5018 firmwareall versions
- qualcomm ipq5028 firmwareall versions
- qualcomm qca1062 firmwareall versions
- qualcomm qca1064 firmwareall versions
- qualcomm qca2062 firmwareall versions
- qualcomm qca2064 firmwareall versions
- qualcomm qca2065 firmwareall versions
- qualcomm qca2066 firmwareall versions
- qualcomm qca6175a firmwareall versions
- qualcomm qca6310 firmwareall versions
- qualcomm qca6335 firmwareall versions
- qualcomm qca6390 firmwareall versions
- qualcomm qca6391 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 Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Mu
- AQT1000, AR8031, AR8035, CSRA6620, CSRA6640, CSRB31024, IPQ5010, IPQ5018, IPQ5028, QCA1062, QCA1064, QCA2062, QCA2064, QCA2065, QCA2066, QCA6175A, QCA6310, QCA6335, QCA6390, QCA6391, QCA6420, QCA6421,affected
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-21479Incorrect Authorization in GraphicsKEV64This week
- CVE-2025-21480Incorrect Authorization in Graphics WindowsKEV64This week
- CVE-2021-1965Possible buffer overflow due to lack of parameter length check during MBSSID scan IE parse in Snapdragon Auto, Snapdragon Compute, Snapdrago40Plan
Published before and after this one in the same product
- ← EarlierCVE-2021-1952Sep 9, 2021 · Possible buffer over read occurs due to lack of length check of request buffer in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivi31Monitor
- ← EarlierCVE-2021-1956Sep 9, 2021 · Improper handling of ASB-U packet with L2CAP channel ID by slave host can lead to interference with piconet in Snapdragon Auto, Snapdragon C26Monitor
- Later →CVE-2021-1962Sep 9, 2021 · Buffer Overflow while processing IOCTL for getting peripheral endpoint information there is no proper validation for input maximum endpoint 26Monitor
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0708 · Sep 7, 2021(Qualcomm Chipset Zafiyeti)
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
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.