CVE-2021-35129

Memory corruption via unchecked Bluetooth command length

Published Jun 14, 2022 · Updated Aug 4, 2024

Memory corruption in Qualcomm Snapdragon BT controllers allows local users to corrupt controller memory via vendor-specific commands. The controller copies command input without properly validating its declared length, allowing oversized input to overwrite controller memory. Exploitation requires local low-privileged access; Qualcomm has not disclosed whether the result is a crash, code execution, or another compromise.

CVSS severity7.8
High
EPSS probability0.16%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Memory corruption in Qualcomm Snapdragon BT controllers allows local users to corrupt controller memory via vendor-specific commands. The controller copies command input without properly validating its declared length, allowing oversized input to overwrite controller memory. Exploitation requires local low-privileged access; Qualcomm has not disclosed whether the result is a crash, code execution, or another compromise.

The record

CVE
CVE-2021-35129
Published
Jun 14, 2022
Updated
Aug 4, 2024
Vendor
Qualcomm
Product
Snapdragon
Classifications
CWE-120
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 14, 2022CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=AR8035, IPQ5010, IPQ5018, IPQ5028, QCA2062, QCA2064, QCA2065, QCA2066, QCA6391, QCA8081, QCA8337, QCC710, QCM6490, QCN6023, QCN6024, QCN6100, QCN6102, QCN6112, QCN6122, QCN6132, QCN9000, QCN9012, QCN9022, QCN9024, QCN9070, QCN9072, QCN9074, QCN9100, QCS6490, SD 8 Gen1 5G, SD 8cx Gen3, SD888, SD888 5G, SDX65, WCD9370, WCD9375, WCD9380, WCD9385, WCN6750, WCN6850, WCN6851, WCN6855, WCN6856, WSA8830, WSA8835

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Qualcomm · Snapdragonversion=AR8035, IPQ5010, IPQ5018, IPQ5028, QCA2062, QCA2064, QCA2065, QCA2066, QCA6391, QCA8081, QCA8337, QCC710, QCM6490, QCN6023, QCN6024, QCN6100, QCN6102, QCN6112, QCN6122, QCN6132, QCN9000, QCN9012, QCN9022, QCN9024, QCN9070, QCN9072, QCN9074, QCN9100, QCS6490, SD 8 Gen1 5G, SD 8cx Gen3, SD888, SD888 5G, SDX65, WCD9370, WCD9375, WCD9380, WCD9385, WCN6750, WCN6850, WCN6851, WCN6855, WCN6856, WSA8830, WSA8835

Published CVSS scores

7.8Qualcomm, Inc.CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
7.2NIST NVDAV:L/AC:L/Au:N/C:C/I:C/A:C

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

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

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo