Skip to main content
VulnerabilityPublished

CVE-2025-27068: 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 6 Aug 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. Immediate inventory and identification of all devices using affected Qualcomm Snapdragon platforms within the organization.
  2. Monitor Qualcomm and device vendors for official patches or firmware updates addressing CVE-2025-27068 and apply them promptly.
  3. Until patches are available, implement strict access controls to limit local user privileges and restrict access to devices that process IOCTL commands.
  4. Employ endpoint detection and response (EDR) solutions to monitor for anomalous behavior indicative of exploitation attempts, such as unusual IOCTL calls or memory access patterns.
  5. Harden device configurations by disabling unnecessary services or interfaces that could be leveraged to trigger the vulnerability.
  6. For critical environments, consider network segmentation to isolate vulnerable devices and reduce attack surface exposure.
  7. Engage with device manufacturers to obtain security advisories and coordinate vulnerability management efforts.
  8. Conduct security awareness training for IT staff to recognize and respond to potential exploitation signs related to this vulnerability.

Description

Memory corruption while processing an IOCTL command with an arbitrary address.

References

Community reviews

Loading reviews…