Skip to main content
VulnerabilityPublished

CVE-2025-47372: Qualcomm Snapdragon · Classic Buffer Overflow

Affects Qualcomm SnapdragonSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.0 Critical.

Data as of 29 Oct 2026, 14:41 UTC

CVSS 3.1 base score
9.0Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 29 Oct 2026.

What to do

AI-suggested

  1. Monitor Qualcomm’s official security advisories and apply patches immediately once they become available for all affected Snapdragon chipset versions.
  2. Implement strict input validation and integrity checks on ELF images and other executable files processed by devices using Snapdragon chips to prevent malformed inputs from triggering the vulnerability.
  3. Restrict local access to devices with affected chipsets by enforcing strong physical security controls and limiting administrative privileges.
  4. Employ runtime protection mechanisms such as memory protection, stack canaries, and address space layout randomization (ASLR) where supported to mitigate exploitation attempts.
  5. Conduct regular security audits and penetration testing focused on embedded systems and mobile devices to detect potential exploitation attempts.
  6. Educate users and administrators about the risks of installing untrusted software or files that could contain corrupted ELF images.
  7. Collaborate with device manufacturers and telecom providers to ensure secure firmware and software update mechanisms are in place to facilitate rapid patch deployment.
  8. Consider network segmentation and monitoring to detect anomalous behavior indicative of exploitation attempts on affected devices.

Description

Memory Corruption when a corrupted ELF image with an oversized file size is read into a buffer without authentication.

References

Community reviews

Loading reviews…