CVE-2025-47380: Qualcomm Snapdragon · Untrusted Pointer Dereference
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.08% 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:H/I:H/A:HExploitation 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Qualcomm, Inc.Snapdragon | Affected
| Fixed in– |
AI-suggested
1. Monitor Qualcomm and device vendors for official patches and apply them promptly once released. 2. Restrict access to IOCTL interfaces related to sensor drivers using strict access control policies and sandboxing to limit local attacker capabilities. 3. Employ device integrity verification and runtime protection mechanisms to detect anomalous memory corruption or unauthorized code execution attempts. 4. Harden endpoint security by limiting local user privileges and disabling unnecessary services that could be leveraged to trigger IOCTL calls. 5. Implement network segmentation and strong authentication to reduce the risk of attackers gaining local access to vulnerable devices. 6. Use endpoint detection and response (EDR) tools to monitor for suspicious activity related to sensor drivers or kernel memory anomalies. 7. Educate users and administrators about the risks of local privilege escalation vulnerabilities and the importance of device security hygiene. 8. For IoT deployments, consider network-level protections and device isolation to contain potential exploitation impacts.
Description
Memory corruption while preprocessing IOCTLs in sensors.