CVE-2021-1921: Possible memory corruption due to Improper handling of hypervisor unmap operations for concurrent memory operations in Snapdragon Auto…
Noroxi assessment
Priority: Monitor (action score 28/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. A low-privileged account is enough. 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
Possible memory corruption due to Improper handling of hypervisor unmap operations for concurrent memory operations in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile
- Published
- Nov 12, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-367
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- 7.0
- CNA · qualcomm
- 7.8
- 0.8 point gap
CVSS:3.1/AV:L/AC:L/PR:L/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 | aqt1000 firmware | cpe:2.3:o:qualcomm:aqt1000_firmware |
| qualcomm | aqt1000 | cpe:2.3:h:qualcomm:aqt1000 |
| 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 | qca6420 firmware | cpe:2.3:o:qualcomm:qca6420_firmware |
| qualcomm | qca6420 | cpe:2.3:h:qualcomm:qca6420 |
| qualcomm | qca6421 firmware | cpe:2.3:o:qualcomm:qca6421_firmware |
| qualcomm | qca6421 | cpe:2.3:h:qualcomm:qca6421 |
| qualcomm | qca6426 firmware | cpe:2.3:o:qualcomm:qca6426_firmware |
| qualcomm | qca6426 | cpe:2.3:h:qualcomm:qca6426 |
and 102 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
- AQT1000, QCA6390, QCA6391, QCA6420, QCA6421, QCA6426, QCA6430, QCA6431, QCA6436, QCA6574AU, QCA6595, QCM6490, QCS6490, QRB5165, QRB5165N, QSM8350, SA6155P, SA8195P, SD 8C, SD 8CX, SD675, SD778G, SD780affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- qualcomm aqt1000 firmwareall versions
- qualcomm qca6390 firmwareall versions
- qualcomm qca6391 firmwareall versions
- qualcomm qca6420 firmwareall versions
- qualcomm qca6421 firmwareall versions
- qualcomm qca6426 firmwareall versions
- qualcomm qca6430 firmwareall versions
- qualcomm qca6431 firmwareall versions
- qualcomm qca6436 firmwareall versions
- qualcomm qca6574au firmwareall versions
- qualcomm qca6595 firmwareall versions
- qualcomm qcm6490 firmwareall versions
- qualcomm qcs6490 firmwareall versions
- qualcomm qrb5165 firmwareall versions
- qualcomm qrb5165n firmwareall versions
- qualcomm qsm8350 firmwareall versions
- qualcomm sa6155p firmwareall versions
- qualcomm sa8195p firmwareall versions
- qualcomm sd 8c firmwareall versions
- qualcomm sd 8cx firmwareall versions
Same product
qualcomm: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-21479Incorrect Authorization in GraphicsKEV64This week
- CVE-2025-21480Incorrect Authorization in Graphics WindowsKEV64This week
- CVE-2021-1965Possible buffer overflow due to lack of parameter length check during MBSSID scan IE parse in Snapdragon Auto, Snapdragon Compute…40Plan
Published before and after this one in the same product
- ← EarlierCVE-2021-1903Nov 12, 2021 · Possible denial of service scenario can occur due to lack of length check on Channel Switch Announcement IE in beacon or probe response…21Monitor
- ← EarlierCVE-2021-1912Nov 12, 2021 · Possible integer overflow can occur due to improper length check while calculating count and grace period in Snapdragon Auto, Snapdragon…31Monitor
- Later →CVE-2021-1979Nov 12, 2021 · Possible buffer overflow due to improper validation of FTM command payload in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity…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.
- 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-367 · Time-of-check Time-of-use (TOCTOU) Race ConditionCVSS vector
CVSS:3.1/AV:L/AC:H/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.
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.