nday
CVE-2021-1905

Qualcomm Multiple Chipsets Use-After-Free Vulnerability

Qualcomm / Multiple Chipsets · Qualcomm, Inc. / Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

Added to KEV 180 days after disclosure. nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

use-after-free
CWE-416, stated by the ADP CISA-ADP, NVD's analysts, and NVD, republishing 134c704f-9b21-4f2e-91b3-4a467353bcc0
local
AV:L in CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA qualcomm
no authentication required
PR:N in CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA qualcomm
no user interaction
UI:N in CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA qualcomm
Qualcomm Snapdragon
affected products in the CVE record: Qualcomm, Inc. · Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapd…CPE names NVD's analysts give as vulnerable: o:qualcomm:apq8009_firmware, o:qualcomm:apq8009w_firmware, o:qualcomm:apq8017_firmware, o:qualcomm:apq8053_firmware, o:qualcomm:apq8064au_firmware, o:qualcomm:apq8096au_firmware, o:qualcomm:mdm9206_firmware, o:qualcomm:mdm9607_firmware, o:qualcomm:mdm9626_firmware, o:qualcomm:mdm9628_firmware and 54 more
chipset / firmware
affected products in the CVE record: Qualcomm · Multiple Chipsets, Qualcomm, Inc. · Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapd…CPE names NVD's analysts give as vulnerable: o:qualcomm:apq8009_firmware, o:qualcomm:apq8009w_firmware, o:qualcomm:apq8017_firmware, o:qualcomm:apq8053_firmware, o:qualcomm:apq8064au_firmware, o:qualcomm:apq8096au_firmware, o:qualcomm:aqt1000_firmware, o:qualcomm:ar8031_firmware, o:qualcomm:ar8035_firmware, o:qualcomm:ar8151_firmware and 386 morethe product type of Qualcomm Snapdragon in nday's product registrynday's type rule vendor:qualcomm
stage
KEV
disclosed
disclosure → KEV
T+180d KEV is date-only
cvss
8.4 HIGH v3.1
KEV due date
2022-05-03

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2021-05-07T09:10Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
≤ 2021-11-03, inferred from KEV
KEVKEV
2021-11-03, date only

Summary

Possible use after free due to improper handling of memory mapping of multiple processes simultaneously. in Snapdragon Auto, Snapdragon Compute, Snapdragon Connectivity, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music, Snapdragon Wearables

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:N
None: no account or authorization needed
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS 3.1 vector from the CVE record, scored by the CNA qualcomm.

Event log

+DISdisclosed

CVE record published by qualcomm. CVSS 8.4, high. CISA's SSVC assessment rates exploitation as active.

src cvelist · nday , bulk import · raw
{
  "id": 18726,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2021-1905",
  "occurred_at": "2021-05-07T09:10:40Z",
  "observed_at": "2026-11-12T15:02:49.796473Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "kev": {
      "reference": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-1905",
      "date_added": "2021-11-03"
    },
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 8.4,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2025-01-29T20:07:39.408546Z",
      "automatable": "no",
      "exploitation": "active",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2021-05-07T09:10:40.000Z",
    "assigner_short_name": "qualcomm"
  }
}
2021-11-03date only, from source
+KEVadded to KEV

CISA added it to the Known Exploited Vulnerabilities catalog, with a remediation deadline of 2022-05-03. Ransomware use: unknown.

src kev · nday , bulk import · raw
{
  "id": 1719,
  "type": "kev_added",
  "source": "kev",
  "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
  "occurred_at": "2021-11-03T00:00:00Z",
  "observed_at": "2026-11-12T13:53:00.018191Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cwes": [
      "CWE-416"
    ],
    "notes": "https://nvd.nist.gov/vuln/detail/CVE-2021-1905",
    "product": "Multiple Chipsets",
    "due_date": "2022-05-03",
    "precision": "day",
    "date_added": "2021-11-03",
    "vendor_project": "Qualcomm",
    "forensic_triage": "No",
    "required_action": "Apply updates per vendor instructions.",
    "vulnerability_name": "Qualcomm Multiple Chipsets Use-After-Free Vulnerability",
    "known_ransomware_campaign_use": "Unknown"
  }
}
≤ 2021-11-03inferred, no direct source
~ITWexploited in the wild

No source says when exploitation began. A KEV listing means it was already happening, so only an upper bound is known. CISA's SSVC assessment rates exploitation as active.

based on kev and CISA's assessment in cvelist

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.