CVE-2025-47363: Qualcomm Snapdragon · Integer Overflow or Wraparound
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 6.8 Medium.
Data as of 26 Oct 2026, 07:57 UTC
- 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:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Feb 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 vendor advisories closely for firmware or software patches addressing CVE-2025-47363. 2. Apply patches promptly once available to eliminate the integer overflow condition. 3. Restrict physical and local access to devices containing affected Snapdragon chipsets to trusted personnel only. 4. Implement device integrity monitoring and anomaly detection to identify signs of exploitation or memory corruption. 5. For high-risk environments, consider isolating vulnerable devices from critical networks until patched. 6. Employ hardware security modules or trusted execution environments where possible to limit impact of memory corruption. 7. Conduct regular security audits and penetration tests focusing on device firmware and hardware interfaces. 8. Educate staff on risks related to physical device access and enforce strict device handling policies. 9. Collaborate with vendors to prioritize vulnerability remediation and secure supply chains. 10. Maintain comprehensive asset inventories to identify all devices with affected Snapdragon versions for targeted mitigation.
Description
Memory corruption when calculating oversized partition sizes without proper checks.