CVE-2025-47376: Qualcomm Snapdragon · Use After Free
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 30 Oct 2026, 11:52 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:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Qualcomm, Inc.Snapdragon | Affected
| Fixed in– |
AI-suggested
- Restrict local access to devices using affected Qualcomm Snapdragon platforms by enforcing strict user permissions and limiting physical access.
- Monitor system logs and IOCTL call patterns for unusual or concurrent access attempts that could indicate exploitation attempts.
- Employ application whitelisting and sandboxing to reduce the risk of malicious code executing IOCTL calls.
- Coordinate with device manufacturers and Qualcomm for timely receipt and deployment of security patches once available.
- For organizations managing fleets of devices, implement automated patch management and vulnerability scanning focused on Qualcomm components.
- Educate users about the risks of installing untrusted applications that could leverage local privileges to exploit this vulnerability.
- In high-security environments, consider network segmentation and endpoint detection solutions to identify anomalous behavior related to this vulnerability.
- Review and harden device configurations to minimize unnecessary IOCTL call exposure and shared buffer usage where possible.
Description
Memory Corruption when concurrent access to shared buffer occurs during IOCTL calls.