Skip to main content
CVE-2025-47387VulnerabilityPublished

CVE-2025-47387: 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, 08:30 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.09% 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 18 Dec 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 and device vendor advisories closely for official patches addressing CVE-2025-47387 and apply them promptly once available. 2. Until patches are released, restrict access to IOCTL interfaces related to JPEG processing by enforcing strict access controls and limiting local user privileges. 3. Employ application whitelisting and endpoint protection to prevent unauthorized local code execution attempts. 4. Conduct thorough audits of devices using affected Snapdragon platforms to identify and isolate vulnerable hardware. 5. Implement network segmentation to limit lateral movement from compromised devices. 6. Educate users on the risks of installing untrusted applications that could exploit local vulnerabilities. 7. For enterprise-managed devices, consider disabling or restricting features that invoke vulnerable IOCTL calls if feasible. 8. Use runtime protection technologies that can detect and block memory corruption attempts. 9. Maintain up-to-date backups and incident response plans to mitigate potential damage from exploitation. 10. Collaborate with device manufacturers to verify patch deployment and device security status.

Description

Memory Corruption when processing IOCTLs for JPEG data without verification.

References

Community reviews

Loading reviews…