Skip to main content
VulnerabilityPublished Updated

CVE-2025-47368: Qualcomm Snapdragon · Buffer Over-read

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 10:12 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 4 Nov 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

To mitigate CVE-2025-47368, organizations and device manufacturers should: 1) Monitor Qualcomm’s advisories closely for official patches or firmware updates addressing this vulnerability and apply them promptly. 2) Restrict access to MCDM IOCTL interfaces to trusted processes only, employing strict access controls and sandboxing techniques to prevent unauthorized local access. 3) Implement runtime protections such as memory protection mechanisms and address space layout randomization (ASLR) where supported by the platform to reduce exploitation likelihood. 4) Conduct thorough security audits of applications and services that interact with the affected Snapdragon components to detect and block attempts to exploit the vulnerability. 5) For enterprise environments, enforce device usage policies limiting installation of untrusted applications and monitor for anomalous local activity indicative of exploitation attempts. 6) Engage in threat hunting and endpoint detection to identify any signs of exploitation, despite no known exploits currently existing. 7) Educate users about the risks of installing unverified software that could leverage local vulnerabilities. These steps go beyond generic patching advice by focusing on access control, runtime defenses, and proactive detection.

Description

Memory corruption when dereferencing an invalid userspace address in a user buffer during MCDM IOCTL processing.

References

Community reviews

Loading reviews…