VulnerabilityPublished 2 Mar 2026

CVE-2025-47371: Qualcomm Snapdragon · Reachable Assertion

Affects Qualcomm SnapdragonSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 29 Oct 2026, 19:04 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 1% 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 2 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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

Affected software

Product	Affected	Fixed in
Qualcomm, Inc.Snapdragon	Affected AR8035 – WSA8845 59 affected builds	Fixed in–

AI-suggested

Monitor Qualcomm and device vendors for official patches or firmware updates addressing CVE-2025-47371 and apply them promptly once available.
Implement network-level filtering and anomaly detection on LTE infrastructure to identify and block malformed RLC packets with invalid transport blocks before they reach end devices.
Deploy LTE base station and radio access network (RAN) security controls to prevent unauthorized injection or replay of malicious LTE packets.
For enterprise and critical IoT deployments, consider fallback connectivity options or redundancy to mitigate transient LTE outages.
Collaborate with mobile network operators to enhance detection of abnormal LTE signaling patterns indicative of exploitation attempts.
Conduct security assessments of devices using affected Snapdragon platforms to evaluate susceptibility and operational impact.
Educate security teams about this vulnerability to improve incident response readiness for transient LTE DoS events.
Where feasible, isolate critical systems from untrusted LTE networks or use VPNs and secure tunnels to reduce exposure.
Encourage Qualcomm and ecosystem partners to improve assertion handling and input validation in LTE protocol stacks to prevent similar issues in the future.

Description

Transient DOS when an LTE RLC packet with invalid TB is received by UE.

Impact

The primary impact of CVE-2025-47371 is a transient denial of service affecting LTE connectivity on devices using vulnerable Qualcomm Snapdragon platforms. This can disrupt mobile broadband services, causing dropped connections, interrupted data sessions, and degraded user experience. For end users, this may manifest as temporary loss of internet access or call drops. For enterprises and critical infrastructure relying on LTE for connectivity—such as IoT deployments, automotive telematics, fixed wireless access, and emergency communication systems—this could lead to operational disruptions and potential safety risks. Although the DoS is transient, repeated exploitation could cause persistent service degradation or device instability. Since the vulnerability does not compromise confidentiality or integrity, data theft or manipulation is not a concern. However, the widespread presence of affected Snapdragon chipsets in smartphones, automotive systems, and wireless modules globally means the attack surface is large. Attackers with access to LTE radio channels could exploit this to disrupt service in targeted areas or against specific users. The lack of required privileges or user interaction lowers the barrier for exploitation, increasing risk in hostile network environments or where attackers can spoof LTE packets.

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
If the assertion statement is required (e.g., for security or reliability), change the invoking code to avoid the conditions that trigger the assertion.
Implementation
Consider changing the assertion to some other less "fatal" error. This might not be easy to implement, since other code may be needed to handle the error.
Implementation
Make sensitive open/close operations non-reachable from directly user-controlled data (e.g. open/close resources)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Mar 2026, 17:34 UTC

WeaknessesCWE-617

Technical details

References

Community reviews

Related threats