Skip to main content
VulnerabilityPublished Updated

CVE-2023-33120: Qualcomm Snapdragon · Use After Free

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

1. Immediate inventory and identification of devices using affected Qualcomm Snapdragon platforms across organizational assets, including mobile phones, IoT devices, automotive systems, and wearables. 2. Apply vendor-supplied patches and firmware updates as soon as they become available; monitor Qualcomm and device manufacturers’ advisories closely. 3. Implement strict access controls to limit local privilege escalation opportunities, including enforcing strong device authentication and restricting physical access to devices. 4. Employ mobile device management (MDM) solutions to enforce security policies, monitor device integrity, and remotely disable or isolate compromised devices. 5. Educate users on the risks of installing untrusted applications or connecting to insecure networks that could facilitate local exploitation. 6. For automotive and IoT deployments, ensure network segmentation and robust intrusion detection to detect anomalous behavior indicative of exploitation attempts. 7. Collaborate with supply chain partners to verify device security postures and ensure timely updates. 8. Consider deploying runtime protection or anomaly detection on critical devices to identify exploitation attempts targeting the ADSP or audio subsystems. 9. Maintain up-to-date backups and incident response plans tailored to mobile and embedded device compromise scenarios.

Description

Memory corruption in Audio when memory map command is executed consecutively in ADSP.

References

Community reviews

Loading reviews…