CVE-2025-27029VulnerabilityPublished 3 Jun 2025

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

Affects Qualcomm SnapdragonSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Immediate mitigation should focus on monitoring and network-level protections to detect and block anomalous traffic patterns that could trigger the tone measurement response buffer processing, such as malformed or unexpected wireless management frames. 2. Organizations should inventory all devices and infrastructure components using affected Qualcomm Snapdragon and related chipsets to assess exposure. 3. Engage with device and equipment vendors to obtain firmware or software updates addressing CVE-2025-27029 as soon as they become available. 4. Until patches are available, consider segmenting vulnerable devices on isolated network segments with strict access controls to limit exposure to untrusted networks. 5. Deploy intrusion detection/prevention systems (IDS/IPS) with updated signatures to detect attempts to exploit this vulnerability once signatures are released. 6. For mobile device fleets, enforce mobile device management (MDM) policies to ensure timely updates and restrict installation of untrusted applications that might attempt to exploit the vulnerability. 7. Implement robust incident response plans to quickly identify and remediate any disruptions caused by exploitation attempts. 8. Collaborate with Qualcomm and industry groups for coordinated vulnerability disclosure and patch deployment strategies.

Description

Transient DOS while processing the tone measurement response buffer when the response buffer is out of range.

Impact

For European organizations, the impact of CVE-2025-27029 can be substantial, especially for enterprises and service providers relying on Qualcomm Snapdragon-based infrastructure and devices. The affected chipsets are widely used in smartphones, wireless access points, IoT devices, and embedded systems. A successful exploitation could lead to transient denial-of-service conditions, causing network disruptions, degraded service quality, or device reboots. This can affect critical communication infrastructure, enterprise mobile devices, and IoT deployments, potentially interrupting business operations, communications, and service availability. In sectors such as telecommunications, manufacturing, healthcare, and smart city deployments, where Qualcomm chipsets are prevalent, this vulnerability could lead to operational downtime and increased maintenance costs. Additionally, transient DoS conditions could be leveraged as part of a larger attack chain to disrupt services or create windows for further exploitation. The lack of required authentication and user interaction increases the risk, as attackers can remotely trigger the vulnerability over the network. Given the widespread use of Qualcomm chipsets in consumer and enterprise devices across Europe, the vulnerability could impact a broad range of organizations, from SMEs to large enterprises and critical infrastructure providers.

CWE-126Buffer Over-read (opens in a new tab)
Variant weakness
The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

docs.qualcomm.com/product/publicresources/securitybulletin/june-2025-bulletin.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 11 Jul 2025, 06:49 UTC

WeaknessesCWE-126

Technical details

References

Community reviews

Related threats