CVE-2025-27059: Qualcomm Snapdragon · Use of Out-of-range Pointer Offset
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 08:11 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:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Oct 2025
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
AI-suggested
Organizations should monitor Qualcomm’s advisories for official patches and apply them promptly once available. Until patches are released, restrict local access to devices running affected Snapdragon platforms by enforcing strict physical security and network segmentation to limit exposure. Employ host-based intrusion detection systems to monitor for abnormal SCM call behavior or memory corruption indicators. Conduct regular firmware and software integrity checks to detect unauthorized modifications. For IoT and embedded devices, ensure secure boot and trusted execution environments are enabled to mitigate exploitation impact. Collaborate with device vendors to confirm patch availability and deployment timelines. Additionally, implement strict privilege management to minimize the number of users with local access and privileges on vulnerable devices. Maintain up-to-date asset inventories to identify all affected devices in the environment for targeted remediation.
Description
Memory corruption while performing SCM call.