CVE-2025-47370VulnerabilityPublished 4 Nov 2025

CVE-2025-47370: Qualcomm Snapdragon · Reachable Assertion

Affects Qualcomm SnapdragonSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

Attack Vector: Adjacent
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: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
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 4 Nov 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 26 Oct 2026.

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. Monitor Qualcomm and device vendor advisories closely for patches or firmware updates addressing CVE-2025-47370 and apply them promptly once available. 2. Implement Bluetooth access controls by disabling Bluetooth LE scanning or connectivity on devices where it is not required, especially in sensitive or critical environments. 3. Use Bluetooth device whitelisting or MAC address filtering to restrict connections to trusted devices only. 4. In enterprise and automotive environments, consider deploying Bluetooth intrusion detection/prevention systems to detect and block malformed connection attempts. 5. Educate users and administrators about the risks of connecting to unknown Bluetooth devices and encourage disabling Bluetooth when not in use. 6. For critical infrastructure, evaluate the feasibility of physical or RF shielding to limit Bluetooth attack surface. 7. Maintain network segmentation to isolate vulnerable devices and limit potential impact of Bluetooth-based disruptions.

Description

Transient DOS when a remote device sends an invalid connection request during BT connectable LE scan.

Impact

For European organizations, the primary impact of CVE-2025-47370 is transient denial of service on devices using affected Qualcomm Snapdragon chipsets. This can disrupt Bluetooth connectivity, affecting mobile devices, automotive systems, and IoT devices that rely on Bluetooth LE for communication. In sectors such as automotive manufacturing, logistics, and mobile communications, this could lead to temporary loss of critical wireless functions, impacting operational continuity and user experience. While the vulnerability does not compromise confidentiality or integrity, availability interruptions could affect business processes, especially in environments with high reliance on Bluetooth-enabled devices. The broad range of affected chipsets means many consumer and enterprise devices across Europe could be vulnerable. The lack of user interaction or privileges required makes exploitation feasible by nearby attackers, increasing risk in public or unsecured environments. However, the transient nature of the DoS limits long-term damage.

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/november-2025-bulletin.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Nov 2025, 04:02 UTC

WeaknessesCWE-617

Technical details

References

Community reviews

Related threats