NVD / CVE Program· CNA qualcomm

CVE-2021-35129: Memory corruption in BT controller due to improper length check while processing vendor specific commands in Snapdragon Compute, Snapdragon

Noroxi assessment

Priority: Monitor (action score 31/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.16% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. 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

Memory corruption in BT controller due to improper length check while processing vendor specific commands in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking

HighCVSS 7.8 · v3.1—No exploit No fix recorded

Memory safety

Published: Jun 14, 2022
Updated: Jun 16, 2026
EPSS: 0.1% · 5th percentile
CWE: CWE-120

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CNA vs NVD score

NVD: 7.8
CNA · qualcomm: 7.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

Is your version affected? Check it

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 help

Affected 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	ar8035 firmware	cpe:2.3:o:qualcomm:ar8035_firmware
qualcomm	ar8035	cpe:2.3:h:qualcomm:ar8035
qualcomm	ipq5010 firmware	cpe:2.3:o:qualcomm:ipq5010_firmware
qualcomm	ipq5010	cpe:2.3:h:qualcomm:ipq5010
qualcomm	ipq5018 firmware	cpe:2.3:o:qualcomm:ipq5018_firmware
qualcomm	ipq5018	cpe:2.3:h:qualcomm:ipq5018
qualcomm	ipq5028 firmware	cpe:2.3:o:qualcomm:ipq5028_firmware
qualcomm	ipq5028	cpe:2.3:h:qualcomm:ipq5028
qualcomm	qca2062 firmware	cpe:2.3:o:qualcomm:qca2062_firmware
qualcomm	qca2062	cpe:2.3:h:qualcomm:qca2062
qualcomm	qca2064 firmware	cpe:2.3:o:qualcomm:qca2064_firmware
qualcomm	qca2064	cpe:2.3:h:qualcomm:qca2064

and 78 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

qualcomm ar8035 firmwareall versions
qualcomm ipq5010 firmwareall versions
qualcomm ipq5018 firmwareall versions
qualcomm ipq5028 firmwareall versions
qualcomm qca2062 firmwareall versions
qualcomm qca2064 firmwareall versions
qualcomm qca2065 firmwareall versions
qualcomm qca2066 firmwareall versions
qualcomm qca6391 firmwareall versions
qualcomm qca8081 firmwareall versions
qualcomm qca8337 firmwareall versions
qualcomm qcc710 firmwareall versions
qualcomm qcm6490 firmwareall versions
qualcomm qcn6023 firmwareall versions
qualcomm qcn6024 firmwareall versions
qualcomm qcn6100 firmwareall versions
qualcomm qcn6102 firmwareall versions
qualcomm qcn6112 firmwareall versions
qualcomm qcn6122 firmwareall versions
qualcomm qcn6132 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 Compute, Snapdragon Connectivity, Snapdragon Consumer Electronics Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking
- AR8035, IPQ5010, IPQ5018, IPQ5028, QCA2062, QCA2064, QCA2065, QCA2066, QCA6391, QCA8081, QCA8337, QCC710, QCM6490, QCN6023, QCN6024, QCN6100, QCN6102, QCN6112, QCN6122, QCN6132, QCN9000, QCN9012, QCN9affected

Same product

qualcomm: all records

Other highest-scoring records for the same primary product.

CVE-2023-33106Use of Out-of-range Pointer Offset in GraphicsKEV
61This week
CVE-2024-49839Buffer Over-read in WLAN Host Cmn
39Monitor
CVE-2024-45569Improper Validation of Array Index in WLAN Host Communication
39Monitor

Published before and after this one in the same product

← EarlierCVE-2021-35102Jun 14, 2022 · Possible buffer overflow due to lack of validation for the length of NAI string read from EFS in Snapdragon Auto, Snapdragon Compute, Snapdr
31Monitor
← EarlierCVE-2021-35111Jun 14, 2022 · Improper validation of tag id while RRC sending tag id to MAC can lead to TOCTOU race condition in Snapdragon Connectivity, Snapdragon Mobil
23Monitor
Later →CVE-2021-35130Jun 14, 2022 · Memory corruption in graphics support layer due to use after free condition in Snapdragon Auto, Snapdragon Consumer IOT, Snapdragon Industri
31Monitor

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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 researchers

Finders, 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

Someone with local access to the system can trigger it.
A low-privileged account is enough.
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: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

CVSS vector

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

nvd-primary

Root cause

When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.

The bug in code

The whole CWE-120 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1char buf[256];
2memcpy(buf, pkt->data, pkt->len);

Fixed

1char buf[256];
2if (pkt->len > sizeof(buf)) {
3  return -EINVAL;
4}
5memcpy(buf, pkt->data, pkt->len);

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)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

www.qualcomm.com/company/product-security/bulletins/april-2022-bulletin

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records