CVE-2021-30349

Improper access control sequence for AC database after memory allocation can lead to possible...

8.2 High

Improper access control sequence for AC database after memory allocation can lead to possible memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking

Attack profile

How easy it is to exploit

Attack vector: Local
Complexity: Low
Privileges needed: High
User interaction: None

What an attacker can affect

Confidentiality: High
Integrity: High
Availability: High

Exploit likelihood

0.17%Down 0.7 points since Jun 15, 2022

What each source reports

CVE List Score used 8.2

Record: CVE-2021-30349
CVSS 3.1: 8.2 HighCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Updated: 2026-11-02

EUVDEUVD-2021-17280 8.2

Record: EUVD-2021-17280
CVSS 3.1: 8.2 HighCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Updated: 2026-11-03

GitHub AdvisoriesGHSA-x83f-gj57-frqr 6.7

Improper access control sequence for AC database after memory allocation can lead to possible...

Record: GHSA-x83f-gj57-frqr
CVSS 3.1: 6.7 MediumCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Weakness: CWE-269
Updated: 2026-11-02

NVD 8.2

Record: CVE-2021-30349
CVSS 3.1: 8.2 HighCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
CVSS 3.1: 6.7 MediumCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CVSS 2.0: 7.2 HighAV:L/AC:L/Au:N/C:C/I:C/A:C
Updated: 2026-11-02

Affected products

Show 130 moreShow less

History

History
Recorded	Changed	Sources
Nov 3, 2026	aliases	EUVD
Nov 2, 2026	first indexed	CVE List, GitHub Advisories, NVD

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2021-30349 is a high vulnerability (CVSS 8.2) in Qualcomm, Inc. Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer Iot, Snapdragon Industrial Iot, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure And Networking, published June 14, 2022. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.17%, the 5th percentile. No source names a fixed version.