CVE-2025-47333: Qualcomm Snapdragon · Use After Free
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 6.6 Medium.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.07% chance of exploitation in 30 days – higher than 0% 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:L/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 6 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Qualcomm, Inc.Snapdragon | Affected
| Fixed in– |
AI-suggested
- Monitor Qualcomm and device vendors for official patches addressing CVE-2025-47333 and apply them promptly once released.
- Restrict local access to devices running affected Snapdragon platforms by enforcing strict access controls and least privilege principles.
- Implement endpoint detection and response (EDR) solutions to monitor for anomalous behavior related to cryptographic operations or memory corruption.
- For automotive and IoT deployments, ensure secure device management and update mechanisms are in place to facilitate rapid patching.
- Conduct security audits of devices using affected platforms to identify potential exploitation attempts or signs of compromise.
- Educate internal teams about the vulnerability and the importance of limiting local privilege escalation vectors.
- Where possible, isolate critical systems using Snapdragon platforms from untrusted networks or users to reduce attack surface.
- Employ runtime protections such as memory protection mechanisms (e.g., ASLR, DEP) that may mitigate exploitation impact.
- Collaborate with suppliers and vendors to understand the vulnerability's impact on embedded devices and coordinate remediation efforts.
- Maintain up-to-date inventories of devices using affected Qualcomm platforms to prioritize patching and risk management.
Description
Memory corruption while handling buffer mapping operations in the cryptographic driver.