Skip to main content
VulnerabilityPublished Updated

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

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 17:16 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 24 Sep 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 26 Oct 2026.

What to do

AI-suggested

  1. Monitor Qualcomm’s official security advisories and apply patches immediately upon release to address CVE-2025-47315.
  2. Until patches are available, restrict or disable guest VM capabilities that allow repeated memory unmap requests to minimize attack surface.
  3. Implement strict access controls and monitoring on local accounts with low privileges to detect and prevent suspicious activities related to memory management.
  4. Employ runtime protection mechanisms such as memory corruption detectors and exploit mitigation technologies (e.g., Control Flow Integrity, Address Space Layout Randomization) on affected devices.
  5. Conduct thorough security assessments of virtualized environments using Snapdragon chipsets to identify and remediate potential exploitation vectors.
  6. Educate system administrators and security teams about the vulnerability’s specifics to enhance detection and response capabilities.
  7. For organizations deploying Snapdragon-based IoT or embedded devices, ensure firmware integrity verification and secure update mechanisms are in place to facilitate timely remediation.
  8. Consider network segmentation and isolation of vulnerable devices to limit potential lateral movement in case of exploitation.

Description

Memory corruption while handling repeated memory unmap requests from guest VM.

References

Community reviews

Loading reviews…