Skip to main content
VulnerabilityPublished

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

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 6.6 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
6.6Medium
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:L/I:H/A:L

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 26 Oct 2026.

What to do

AI-suggested

  1. Monitor Qualcomm and device manufacturers for official patches or firmware updates addressing CVE-2025-21426 and apply them promptly once available.
  2. Implement strict application whitelisting and privilege restrictions on devices using affected Snapdragon platforms to limit the ability of untrusted code to execute or interact with the camera subsystem.
  3. Employ runtime protection mechanisms such as memory protection and control-flow integrity on devices where feasible to reduce the risk of exploitation from buffer overflows.
  4. Conduct thorough security assessments of AR and IoT devices in the environment, focusing on those using the affected chipsets, to identify potential exposure.
  5. Limit physical and local access to sensitive devices, as exploitation requires local access with low privileges.
  6. Use mobile device management (MDM) solutions to enforce security policies and monitor for anomalous behavior indicative of exploitation attempts.
  7. Educate users and administrators about the risks of installing untrusted applications or connecting unknown peripherals that might trigger the vulnerability.
  8. For organizations deploying AR or IoT solutions, consider network segmentation and strict access controls to isolate vulnerable devices and minimize lateral movement in case of compromise.

Description

Memory corruption while processing camera TPG write request.

References

Community reviews

Loading reviews…