CVE-2021-30313: Use after free condition can occur in wired connectivity due to a race condition while creating and deleting folders in Snapdragon Auto…
Noroxi assessment
Priority: Monitor (action score 25/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.10% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
- 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
Use after free condition can occur in wired connectivity due to a race condition while creating and deleting folders in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables, Snapdragon Wired Infrastructure and Networking
- Published
- Jan 13, 2022
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-362
Report tools
Action score
25
Low priority for now.
- CVSS
- 25 / 40 · 6.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- 6.4
- CNA · qualcomm
- 6.7
- 0.3 point gap
CVSS:3.1/AV:L/AC:L/PR:H/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.
Is your version affected? Check itNoroxi 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 | apq8096au firmware | cpe:2.3:o:qualcomm:apq8096au_firmware |
| qualcomm | apq8096au | cpe:2.3:h:qualcomm:apq8096au |
| 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 | ar9380 firmware | cpe:2.3:o:qualcomm:ar9380_firmware |
| qualcomm | ar9380 | cpe:2.3:h:qualcomm:ar9380 |
| qualcomm | csr8811 firmware | cpe:2.3:o:qualcomm:csr8811_firmware |
| qualcomm | csr8811 | cpe:2.3:h:qualcomm:csr8811 |
| qualcomm | csra6620 firmware | cpe:2.3:o:qualcomm:csra6620_firmware |
| qualcomm | csra6620 | cpe:2.3:h:qualcomm:csra6620 |
and 188 more
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, Snapdragon Wired In
- APQ8096AU, AR8031, AR8035, AR9380, CSR8811, CSRA6620, CSRA6640, IPQ4018, IPQ4019, IPQ4028, IPQ4029, IPQ5010, IPQ5018, IPQ5028, IPQ6000, IPQ6010, IPQ6018, IPQ6028, IPQ8064, IPQ8065, IPQ8068, IPQ8069, Iaffected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm apq8096au firmwareall versions
- qualcomm ar8031 firmwareall versions
- qualcomm ar8035 firmwareall versions
- qualcomm ar9380 firmwareall versions
- qualcomm csr8811 firmwareall versions
- qualcomm csra6620 firmwareall versions
- qualcomm csra6640 firmwareall versions
- qualcomm ipq4018 firmwareall versions
- qualcomm ipq4019 firmwareall versions
- qualcomm ipq4028 firmwareall versions
- qualcomm ipq4029 firmwareall versions
- qualcomm ipq5010 firmwareall versions
- qualcomm ipq5018 firmwareall versions
- qualcomm ipq5028 firmwareall versions
- qualcomm ipq6000 firmwareall versions
- qualcomm ipq6010 firmwareall versions
- qualcomm ipq6018 firmwareall versions
- qualcomm ipq6028 firmwareall versions
- qualcomm ipq8064 firmwareall versions
- qualcomm ipq8065 firmwareall versions
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-14045Possible buffer overflow while processing clientlog and serverlog due to lack of validation of data received in logs in Snapdragon Auto…39Monitor
- CVE-2021-35117An Out of Bounds read may potentially occur while processing an IBSS beacon, in Snapdragon Auto, Snapdragon Compute, Snapdragon…36Monitor
- CVE-2020-11126Possible out of bound read while WLAN frame parsing due to lack of check for body and header length in Snapdragon Auto, Snapdragon Compute…36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2020-11160Jun 9, 2021 · Resource leakage issue during dci client registration due to reference count is not decremented if dci client registration fails in…26Monitor
- ← EarlierCVE-2021-1929Sep 8, 2021 · Lack of strict validation of bootmode can lead to information disclosure in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity…22Monitor
- Later →CVE-2021-30324Feb 11, 2022 · Possible out of bound write due to lack of boundary check for the maximum size of buffer when sending a DCI packet to remote process in…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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- Special conditions such as timing or configuration are required.
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
- High
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/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)
ATT&CK techniques
—
Change log (0)
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.