Skip to content
Noroxi
NVD / CVE Program· CNA qualcomm

CVE-2020-11261: Memory corruption due to improper check to return error when user application requests memory allocation of a huge size in Snapdragon Auto,

Noroxi assessment

Priority: This week (action score 61/100)

  • CISA has confirmed exploitation in the wild (Dec 1, 2021). Remediation deadline for US federal agencies: Jun 1, 2022.
  • Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 74.8% of all records.
  • 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.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Don’t wait for the next maintenance window. Until a fix is released, restrict access to the affected component and 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 · CISA KEV · FIRST EPSS

Memory corruption due to improper check to return error when user application requests memory allocation of a huge size in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

HighCVSS 7.8 · v3.1KEVWeaponized No fix recorded
Published
Jun 9, 2021
Updated
Jun 16, 2026
EPSS
1.5% · 74th percentile

Report tools

JSON

Action score

61

This week

Don’t wait for the next maintenance window.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
30 / 30 · Listed
EPSS
0 / 30 · 1.5%

CISA SSVC decision

Exploitation
active
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Actively exploited in the wild

CISA added this to its Known Exploited Vulnerabilities catalog on Dec 1, 2021. That signals real attacks, not theory.

Remediation deadline for US federal agencies: Jun 1, 2022.

Get told when this record changes

  • In CISA KEV: exploitation in the wild confirmed
  • Weaponized exploit exists
  • No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2020-11261

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for qualcomm records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
qualcommapq8009 firmware
qualcommapq8009
qualcommapq8009w firmware
qualcommapq8009w
qualcommapq8017 firmware
qualcommapq8017
qualcommapq8037 firmware
qualcommapq8037
qualcommapq8053 firmware
qualcommapq8053
qualcommapq8064au firmware
qualcommapq8064au

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 apq8009 firmwareall versions
  • qualcomm apq8009w firmwareall versions
  • qualcomm apq8017 firmwareall versions
  • qualcomm apq8037 firmwareall versions
  • qualcomm apq8053 firmwareall versions
  • qualcomm apq8064au firmwareall versions
  • qualcomm apq8096au firmwareall versions
  • qualcomm aqt1000 firmwareall versions
  • qualcomm ar8031 firmwareall versions
  • qualcomm ar8035 firmwareall versions
  • qualcomm ar8151 firmwareall versions
  • qualcomm csra6620 firmwareall versions
  • qualcomm csra6640 firmwareall versions
  • qualcomm csrb31024 firmwareall versions
  • qualcomm fsm10055 firmwareall versions
  • qualcomm fsm10056 firmwareall versions
  • qualcomm mdm9650 firmwareall versions
  • qualcomm msm8909w firmwareall versions
  • qualcomm msm8917 firmwareall versions
  • qualcomm msm8920 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 Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

    • APQ8009, APQ8009W, APQ8017, APQ8037, APQ8053, APQ8064AU, APQ8096AU, AQT1000, AR8031, AR8035, AR8151, CSRA6620, CSRA6640, CSRB31024, FSM10055, FSM10056, MDM9650, MSM8909W, MSM8917, MSM8920, MSM8937, MSaffected

Same product

qualcomm: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-1905Possible use after free due to improper handling of memory mapping of multiple processes simultaneously.KEV
    61This week
  • CVE-2021-1906Improper handling of address deregistration on failure can lead to new GPU address allocation failure.KEV
    52Plan
  • CVE-2020-3657u'Remote code execution can happen by sending a carefully crafted POST query when Device configuration is accessed from a tethered client th
    47Plan

Published before and after this one in the same product

  • ← EarlierCVE-2020-11239Jun 9, 2021 · Use after free issue when importing a DMA buffer by using the CPU address of the buffer due to attachment is not cleaned up properly in Snap
    31Monitor
  • ← EarlierCVE-2020-11241Jun 9, 2021 · Out of bound read will happen if EAPOL Key length is less than expected while processing NAN shared key descriptor attribute in Snapdragon A
    30Monitor
  • Later →CVE-2020-11262Jun 9, 2021 · A race between command submission and destroying the context can cause an invalid context being added to the list leads to use after free is
    28Monitor

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

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

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.

  1. Published
  2. CISA KEV+175 d
  3. TodayNov 9, 2026+1979 d

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 researchers

Finders, 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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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-787 · Out-of-bounds Write

CVSS 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.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records