CVE-2025-27039: Qualcomm Snapdragon · Detection of Error Condition Without Action
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 6.6 Medium.
Data as of 26 Oct 2026, 06:26 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:L/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 2026-10-26.
What to do
AI-suggested
Organizations and users should monitor Qualcomm’s advisories for official patches and apply them promptly once available. Until patches are released, restrict local access to trusted users and processes to reduce exploitation risk. Employ mobile device management (MDM) solutions to enforce strict application controls and limit installation of untrusted or unnecessary apps that might exploit local vulnerabilities. Implement robust input validation and error handling in custom software interacting with Qualcomm components to detect and mitigate abnormal IOCTL calls. Conduct regular security audits and penetration testing focusing on local privilege escalation vectors. For manufacturers and developers, consider integrating enhanced error handling mechanisms to ensure detected errors trigger appropriate corrective actions, preventing memory corruption. Maintain up-to-date firmware and OS versions to benefit from security improvements and mitigations that may indirectly reduce risk.
Description
Memory corruption may occur while processing IOCTL call for DMM/WARPNCC CONFIG request.