CVE-2021-30257: Possible out of bound read or write in VR service due to lack of validation of DSP selection values in Snapdragon Compute, Snapdragon…
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 out of bound read or write in VR service due to lack of validation of DSP selection values in Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT
- Published
- Oct 20, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-125
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
- 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.
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 | apq8017 firmware | cpe:2.3:o:qualcomm:apq8017_firmware |
| qualcomm | apq8017 | cpe:2.3:h:qualcomm:apq8017 |
| qualcomm | apq8053 firmware | cpe:2.3:o:qualcomm:apq8053_firmware |
| qualcomm | apq8053 | cpe:2.3:h:qualcomm:apq8053 |
| qualcomm | aqt1000 firmware | cpe:2.3:o:qualcomm:aqt1000_firmware |
| qualcomm | aqt1000 | cpe:2.3:h:qualcomm:aqt1000 |
| qualcomm | msm8917 firmware | cpe:2.3:o:qualcomm:msm8917_firmware |
| qualcomm | msm8917 | cpe:2.3:h:qualcomm:msm8917 |
| qualcomm | msm8953 firmware | cpe:2.3:o:qualcomm:msm8953_firmware |
| qualcomm | msm8953 | cpe:2.3:h:qualcomm:msm8953 |
| qualcomm | qca6390 firmware | cpe:2.3:o:qualcomm:qca6390_firmware |
| qualcomm | qca6390 | cpe:2.3:h:qualcomm:qca6390 |
and 142 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 Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT
- APQ8017, APQ8053, AQT1000, MSM8917, MSM8953, QCA6390, QCA6391, QCA6420, QCA6426, QCA6430, QCA6436, QCM2290, QCM4290, QCM6125, QCM6490, QCS2290, QCS4290, QCS605, QCS6125, QCS6490, Qualcomm215, SD 636, 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 apq8017 firmwareall versions
- qualcomm apq8053 firmwareall versions
- qualcomm aqt1000 firmwareall versions
- qualcomm msm8917 firmwareall versions
- qualcomm msm8953 firmwareall versions
- qualcomm qca6390 firmwareall versions
- qualcomm qca6391 firmwareall versions
- qualcomm qca6420 firmwareall versions
- qualcomm qca6426 firmwareall versions
- qualcomm qca6430 firmwareall versions
- qualcomm qca6436 firmwareall versions
- qualcomm qcm2290 firmwareall versions
- qualcomm qcm4290 firmwareall versions
- qualcomm qcm6125 firmwareall versions
- qualcomm qcm6490 firmwareall versions
- qualcomm qcs2290 firmwareall versions
- qualcomm qcs4290 firmwareall versions
- qualcomm qcs605 firmwareall versions
- qualcomm qcs6125 firmwareall versions
- qualcomm qcs6490 firmwareall versions
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-21483Improper Restriction of Operations within the Bounds of a Memory Buffer in Data Network Stack & Connectivity39Monitor
- CVE-2022-25686Memory corruption in video module due to buffer overflow while processing WAV file in Snapdragon Auto, Snapdragon Compute, Snapdragon…39Monitor
- CVE-2022-25657Memory corruption due to buffer overflow occurs while processing invalid MKV clip which has invalid seek header in Snapdragon Auto…39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-1985Oct 20, 2021 · Possible buffer over read due to lack of data length check in QVR Service configuration in Snapdragon Auto, Snapdragon Compute, Snapdragon…28Monitor
- ← EarlierCVE-2021-30256Oct 20, 2021 · Possible stack overflow due to improper validation of camera name length before copying the name in VR Service in Snapdragon Compute…31Monitor
- Later →CVE-2021-30258Oct 20, 2021 · Possible buffer overflow due to improper size calculation of payload received in VR service in Snapdragon Auto, Snapdragon Compute…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.
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-125 · Out-of-bounds ReadCVSS 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.