NVD / CVE Program· CNA qualcomm

CVE-2021-30262: Improper validation of a socket state when socket events are being sent to clients can lead to invalid access of memory in Snapdragon Auto,

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.15% (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

Improper validation of a socket state when socket events are being sent to clients can lead to invalid access of memory in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

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

Memory safety

Published: Jan 3, 2022
Updated: Jun 16, 2026
EPSS: 0.1% · 4th percentile
CWE: CWE-416

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: 8.4; 0.6 point gap

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

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	apq8009w firmware	cpe:2.3:o:qualcomm:apq8009w_firmware
qualcomm	apq8009w	cpe:2.3:h:qualcomm:apq8009w
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

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 apq8009w firmwareall versions
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 fsm10055 firmwareall versions
qualcomm fsm10056 firmwareall versions
qualcomm mdm9150 firmwareall versions
qualcomm mdm9640 firmwareall versions
qualcomm msm8909w firmwareall versions
qualcomm qca6174a firmwareall versions
qualcomm qca6390 firmwareall versions
qualcomm qca6391 firmwareall versions
qualcomm qca6426 firmwareall versions
qualcomm qca6436 firmwareall versions
qualcomm qca6564 firmwareall versions
qualcomm qca6564a firmwareall versions
qualcomm qca6564au 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 IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables
- APQ8009W, AQT1000, AR8031, AR8035, CSRA6620, CSRA6640, CSRB31024, FSM10055, FSM10056, MDM9150, MDM9640, MSM8909W, QCA6174A, QCA6390, QCA6391, QCA6426, QCA6436, QCA6564, QCA6564A, QCA6564AU, QCA6574, Qaffected

Same product

qualcomm: all records

Other highest-scoring records for the same primary product.

CVE-2022-22086Memory corruption in video due to double free while parsing 3gp clip with invalid meta data atoms in Snapdragon Auto, Snapdragon Compute, Sn
39Monitor
CVE-2021-35104Possible buffer overflow due to improper parsing of headers while playing the FLAC audio clip in Snapdragon Auto, Snapdragon Compute, Snapdr
39Monitor
CVE-2021-30341Improper buffer size validation of DSM packet received can lead to memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Conn
39Monitor

Published before and after this one in the same product

← EarlierCVE-2021-1947Sep 17, 2021 · Use-after-free vulnerability in kernel graphics driver because of storing an invalid pointer in Snapdragon Compute, Snapdragon Connectivity,
31Monitor
← EarlierCVE-2021-1936Oct 20, 2021 · Null pointer dereference can occur due to lack of null check for user provided input in Snapdragon Auto, Snapdragon Compute, Snapdragon Conn
30Monitor
Later →CVE-2021-30268Jan 3, 2022 · Possible heap Memory Corruption Issue due to lack of input validation when sending HWTC IQ Capture command in Snapdragon Auto, Snapdragon Co
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.

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 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-416 · Use After Free

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

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

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

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

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

www.qualcomm.com/company/product-security/bulletins/december-2021-bulletin

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

All records