CVE-2025-21429VulnerabilityPublished 7 Apr 2025Updated 26 Feb 2026

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

Affects Qualcomm SnapdragonSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 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 17% 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 7 Apr 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-25.

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's official security advisories and promptly apply firmware and software updates once patches are released for affected Snapdragon platforms and wireless modules. 2. Implement network-level protections such as Wi-Fi intrusion detection/prevention systems (IDS/IPS) to detect and block malformed or suspicious ADD TS requests that could trigger the vulnerability. 3. For enterprise environments, segment wireless networks and restrict access to critical systems to minimize exposure. 4. Collaborate with device manufacturers and vendors to ensure timely patch deployment across all affected devices in the organization’s inventory. 5. Employ anomaly detection tools to monitor for unusual wireless connection behaviors indicative of exploitation attempts. 6. In automotive and IoT deployments, consider fallback communication methods or redundancy to maintain availability if devices become unresponsive. 7. Educate security teams about this vulnerability to prepare for incident response related to potential denial of service events. 8. Where possible, disable or restrict QoS features related to ADD TS requests temporarily until patches are applied, balancing functionality and security. 9. Engage with Qualcomm support channels for guidance on interim mitigations specific to device models in use.

Description

Memory corruption occurs while connecting a STA to an AP and initiating an ADD TS request.

Impact

This vulnerability poses a significant risk to organizations and end-users relying on Qualcomm Snapdragon-based devices, which include a large portion of smartphones, automotive infotainment systems, IoT devices, and wearable technology worldwide. The primary impact is denial of service, where an attacker can remotely trigger memory corruption leading to device crashes or wireless subsystem failures, resulting in loss of connectivity or device unavailability. This can disrupt critical communications, especially in automotive or industrial IoT contexts where Snapdragon platforms are embedded. The broad range of affected products means that many device types and manufacturers are potentially vulnerable, increasing the attack surface. Enterprises with mobile fleets, telecommunication providers, and automotive manufacturers could face operational disruptions. Although confidentiality and integrity are not directly compromised, the availability impact alone can cause significant business interruptions, safety risks in automotive scenarios, and degraded user experience. The lack of required privileges or user interaction lowers the barrier for attackers to exploit this flaw remotely, increasing the likelihood of attacks once exploit code becomes available.

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 19:49 UTC

WeaknessesCWE-126

Technical details

References

Community reviews

Related threats