Skip to main content
CVE-2025-27069VulnerabilityPublished

CVE-2025-27069: Qualcomm Snapdragon · Untrusted Pointer Dereference

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

To mitigate CVE-2025-27069, European organizations should: 1) Monitor Qualcomm and device vendors for official patches or firmware updates addressing this vulnerability and prioritize their deployment across all affected devices. 2) Implement strict access controls and endpoint security measures to limit local access to devices, reducing the risk of exploitation by unauthorized users. 3) Employ device management solutions to inventory and track devices using affected Snapdragon chipsets, enabling targeted remediation efforts. 4) Restrict installation of untrusted applications and enforce application whitelisting policies to prevent malicious code execution that could leverage this vulnerability. 5) Enhance network segmentation to isolate critical systems and reduce lateral movement opportunities in case of compromise. 6) Conduct regular security audits and penetration testing focusing on mobile and embedded device security to identify potential exploitation paths. 7) Educate users and administrators about the risks associated with local privilege escalation vulnerabilities and the importance of timely updates. Since no patches are currently available, organizations should also consider temporary compensating controls such as disabling unnecessary services or interfaces that process DDI commands if feasible.

Description

Memory corruption while processing DDI command calls.

References

Community reviews

Loading reviews…