CVE-2020-11220: While processing storage SCM commands there is a time of check or time of use window where a pointer used could be invalid at a specific tim
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.13% (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
While processing storage SCM commands there is a time of check or time of use window where a pointer used could be invalid at a specific time while executing the storage SCM call in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking
- Published
- Mar 17, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-367
Report tools
Action score
25
Monitor
Low priority for now.
- CVSS
- 25 / 40 · 6.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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
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 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 | ar8035 firmware | cpe:2.3:o:qualcomm:ar8035_firmware |
| qualcomm | ar8035 | cpe:2.3:h:qualcomm:ar8035 |
| qualcomm | pm4125 firmware | cpe:2.3:o:qualcomm:pm4125_firmware |
| qualcomm | pm4125 | cpe:2.3:h:qualcomm:pm4125 |
| qualcomm | pm4250 firmware | cpe:2.3:o:qualcomm:pm4250_firmware |
| qualcomm | pm4250 | cpe:2.3:h:qualcomm:pm4250 |
| qualcomm | pm6125 firmware | cpe:2.3:o:qualcomm:pm6125_firmware |
| qualcomm | pm6125 | cpe:2.3:h:qualcomm:pm6125 |
| qualcomm | pm6150 firmware | cpe:2.3:o:qualcomm:pm6150_firmware |
| qualcomm | pm6150 | cpe:2.3:h:qualcomm:pm6150 |
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 aqt1000 firmwareall versions
- qualcomm ar8035 firmwareall versions
- qualcomm pm4125 firmwareall versions
- qualcomm pm4250 firmwareall versions
- qualcomm pm6125 firmwareall versions
- qualcomm pm6150 firmwareall versions
- qualcomm pm6150a firmwareall versions
- qualcomm pm6150l firmwareall versions
- qualcomm pm6350 firmwareall versions
- qualcomm pm640a firmwareall versions
- qualcomm pm640l firmwareall versions
- qualcomm pm640p firmwareall versions
- qualcomm pm7250b firmwareall versions
- qualcomm pm8004 firmwareall versions
- qualcomm pm8005 firmwareall versions
- qualcomm pm8008 firmwareall versions
- qualcomm pm8350 firmwareall versions
- qualcomm pm855 firmwareall versions
- qualcomm pm855a firmwareall versions
- qualcomm pm855b 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 Industrial IOT, Snapdragon Mobile, Snapdragon Wired Infrastructure and Networking
- AQT1000, AR8035, PM4125, PM4250, PM6125, PM6150, PM6150A, PM6150L, PM6350, PM640A, PM640L, PM640P, PM7250B, PM8004, PM8005, PM8008, PM8350, PM855, PM855A, PM855B, PM855L, PM855P, PM8998, PMD9655, PMI6affected
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, Snapdrago40Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-11281Feb 22, 2021 · Allowing RTT frames to be linked with non randomized MAC address by comparing the sequence numbers can lead to information disclosure.30Monitor
- ← EarlierCVE-2020-3664Feb 22, 2021 · Out of bound read access in hypervisor due to an invalid read access attempt by passing invalid addresses in Snapdragon Auto, Snapdragon Com24Monitor
- Later →CVE-2020-11228Mar 17, 2021 · Part of RPM region was not protected from xblSec itself due to improper policy and leads to unprivileged access in Snapdragon Auto, Snapdrag31Monitor
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 researchersFinders, 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.
- 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-367 · Time-of-check Time-of-use (TOCTOU) Race ConditionCVSS 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.
Change log
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.