CVE-2025-27073VulnerabilityPublished 6 Aug 2025

CVE-2025-27073: Qualcomm Snapdragon · Reachable Assertion

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 12% 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 6 Aug 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

Mitigation should focus on proactive network and device management strategies tailored to the affected Qualcomm platforms. Organizations should: 1) Monitor vendor advisories closely for official patches or firmware updates addressing CVE-2025-27073 and prioritize timely deployment once available. 2) Implement network segmentation and isolation for devices using affected chipsets to limit exposure and contain potential DoS impacts. 3) Employ IPv6 traffic filtering and anomaly detection to identify and block malformed or suspicious NDP packets that could trigger the assertion failure. 4) Use network intrusion prevention systems (IPS) with updated signatures to detect exploitation attempts targeting NDP vulnerabilities. 5) For critical infrastructure, consider fallback mechanisms or redundant network paths to maintain availability during transient outages. 6) Engage with device and equipment vendors to confirm vulnerability status and remediation timelines, ensuring coordinated patch management. 7) Educate IT and security teams on the specific nature of this vulnerability to enhance incident response readiness. These measures go beyond generic advice by focusing on network protocol-level defenses, vendor coordination, and operational continuity planning specific to Qualcomm Snapdragon-based environments.

Description

Transient DOS while creating NDP instance.

Impact

For European organizations, the impact of CVE-2025-27073 could be significant due to the widespread use of Qualcomm Snapdragon chipsets in mobile devices, IoT infrastructure, and networking hardware. A transient DoS affecting network protocol handling could disrupt critical communications, especially in environments relying on IPv6 networking. Enterprises with large mobile workforces using affected Snapdragon-based smartphones may experience temporary loss of network connectivity, impacting productivity and communication. IoT deployments in smart buildings, industrial automation, or smart city infrastructure using affected platforms could face intermittent outages, potentially affecting operational continuity and safety systems. Telecommunications providers and network operators using Qualcomm-based equipment might see service degradation or outages, impacting end-users and business customers. The vulnerability's exploitation does not require authentication or user interaction, increasing the risk of remote attacks. While no data confidentiality or integrity loss is indicated, the availability impact could disrupt services and cause operational downtime. Given the critical role of networking in European digital infrastructure and the increasing adoption of IPv6, this vulnerability poses a tangible risk to service reliability and business continuity.

Summary

CVE-2025-27073 is a high-severity vulnerability identified in a broad range of Qualcomm Snapdragon platforms and related chipsets. The vulnerability is classified as CWE-617, which corresponds to a Reachable Assertion flaw. Specifically, this vulnerability manifests as a transient Denial of Service (DoS) condition triggered during the creation of a Neighbor Discovery Protocol (NDP) instance. NDP is a critical component in IPv6 networking, responsible for functions such as address autoconfiguration and discovery of other network nodes. The assertion failure indicates that under certain conditions, the system encounters an unexpected state that causes it to halt or crash temporarily, disrupting normal operation. The vulnerability affects an extensive list of Qualcomm products, including multiple Snapdragon mobile platforms (e.g., Snapdragon 8 Gen 1, 8 Gen 2, 865 5G), FastConnect wireless subsystems, Immersive Home platforms, IPQ series, QCA series, and various modem and wireless connectivity chips. The CVSS v3.1 base score is 7.5, reflecting a high severity with network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and impact limited to availability (A:H) without affecting confidentiality or integrity. No known exploits are currently reported in the wild, and no patches have been linked yet. The vulnerability could be exploited remotely by an unauthenticated attacker to cause temporary service disruption on affected devices by triggering the assertion failure during NDP instance creation. This could impact network connectivity and availability on devices using these chipsets, including smartphones, IoT devices, automotive systems, and enterprise networking equipment that rely on Qualcomm Snapdragon components for networking functions.

CWE-617Reachable Assertion (opens in a new tab)
Base weakness
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
Implementation
Make sensitive open/close operation non reachable by directly user-controlled data (e.g. open/close resources)
Implementation · Input Validation
Perform input validation on user data.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 6 Aug 2025, 08:03 UTC

WeaknessesCWE-617

Technical details

References

Community reviews

Related threats