CVE-2021-30311: Possible heap overflow due to lack of index validation before allocating and writing to heap buffer in Snapdragon Auto, Snapdragon Compute…
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
Possible heap overflow due to lack of index validation before allocating and writing to heap buffer in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile
- Published
- Jan 13, 2022
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-129
Report tools
Action score
31
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.
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 | ar8035 firmware | cpe:2.3:o:qualcomm:ar8035_firmware |
| qualcomm | ar8035 | cpe:2.3:h:qualcomm:ar8035 |
| qualcomm | qca6390 firmware | cpe:2.3:o:qualcomm:qca6390_firmware |
| qualcomm | qca6390 | cpe:2.3:h:qualcomm:qca6390 |
| qualcomm | qca6391 firmware | cpe:2.3:o:qualcomm:qca6391_firmware |
| qualcomm | qca6391 | cpe:2.3:h:qualcomm:qca6391 |
| qualcomm | qca6426 firmware | cpe:2.3:o:qualcomm:qca6426_firmware |
| qualcomm | qca6426 | cpe:2.3:h:qualcomm:qca6426 |
| qualcomm | qca6436 firmware | cpe:2.3:o:qualcomm:qca6436_firmware |
| qualcomm | qca6436 | cpe:2.3:h:qualcomm:qca6436 |
| qualcomm | qca6574a firmware | cpe:2.3:o:qualcomm:qca6574a_firmware |
| qualcomm | qca6574a | cpe:2.3:h:qualcomm:qca6574a |
and 122 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 Industrial IOT, Snapdragon Mobile
- AR8035, QCA6390, QCA6391, QCA6426, QCA6436, QCA6574A, QCA6574AU, QCA6595AU, QCA6696, QCA8081, QCA8337, QCM6490, QCS6490, QCX315, SA515M, SD 675, SD 8 Gen1 5G, SD460, SD480, SD662, SD665, SD675, SD678,affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm ar8035 firmwareall versions
- qualcomm qca6390 firmwareall versions
- qualcomm qca6391 firmwareall versions
- qualcomm qca6426 firmwareall versions
- qualcomm qca6436 firmwareall versions
- qualcomm qca6574a firmwareall versions
- qualcomm qca6574au firmwareall versions
- qualcomm qca6595au firmwareall versions
- qualcomm qca6696 firmwareall versions
- qualcomm qca8081 firmwareall versions
- qualcomm qca8337 firmwareall versions
- qualcomm qcm6490 firmwareall versions
- qualcomm qcs6490 firmwareall versions
- qualcomm qcx315 firmwareall versions
- qualcomm sa515m firmwareall versions
- qualcomm sd 675 firmwareall versions
- qualcomm sd 8 gen1 5g firmwareall versions
- qualcomm sd460 firmwareall versions
- qualcomm sd480 firmwareall versions
- qualcomm sd662 firmwareall versions
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-33106Use of Out-of-range Pointer Offset in GraphicsKEV61This week
- CVE-2024-49839Buffer Over-read in WLAN Host Cmn39Monitor
- CVE-2024-45569Improper Validation of Array Index in WLAN Host Communication39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-30301Jan 13, 2022 · Possible denial of service due to out of memory while processing RRC and NAS OTA message in Snapdragon Auto, Snapdragon Industrial IOT…30Monitor
- ← EarlierCVE-2021-30307Jan 13, 2022 · Possible denial of service due to improper validation of DNS response when DNS client requests with PTR, NAPTR or SRV query type in…30Monitor
- Later →CVE-2021-30326Feb 11, 2022 · Possible assertion due to improper size validation while processing the DownlinkPreemption IE in an RRC Reconfiguration/RRC Setup message…30Monitor
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.
- 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-129 · Improper Validation of Array IndexCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/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.