Skip to main content
CVE-2025-27056VulnerabilityPublished

CVE-2025-27056: Qualcomm Snapdragon · Use After Free

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% 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 8 Jul 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-25.

What to do

AI-suggested

1. Immediate inventory and identification of all devices using affected Qualcomm Snapdragon chipsets within the organization, including mobile phones, tablets, wearables, and IoT devices. 2. Monitor Qualcomm and device manufacturers for official patches or firmware updates addressing CVE-2025-27056 and apply them promptly once available. 3. Implement strict access controls and endpoint security measures to limit local access to devices, including enforcing strong authentication and device lockdown policies. 4. Employ mobile device management (MDM) solutions to enforce security policies, monitor device health, and remotely isolate or wipe compromised devices. 5. Educate users about the risks of physical device access by unauthorized personnel and encourage reporting of lost or stolen devices immediately. 6. For critical environments, consider network segmentation to reduce the risk of compromised devices being used as pivot points. 7. Use runtime protection and anomaly detection tools on endpoints to detect unusual behavior that could indicate exploitation attempts. 8. Regularly audit and update device firmware and software to minimize exposure to known vulnerabilities. 9. Collaborate with vendors and security communities to share threat intelligence and stay informed about emerging exploit techniques related to this vulnerability.

Description

Memory corruption during sub-system restart while processing clean-up to free up resources.

References

Community reviews

Loading reviews…