CVE-2025-21463VulnerabilityPublished 3 Jun 2025

CVE-2025-21463: 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, 08:30 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 14% 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 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

Mitigation should focus on a multi-layered approach: 1) Immediate network-level controls: Deploy wireless intrusion detection/prevention systems (WIDS/WIPS) capable of detecting and blocking malformed beacon frames or anomalous EHT IE patterns to prevent exploitation attempts. 2) Firmware and driver updates: Monitor Qualcomm and device vendor advisories closely and apply patches promptly once available. Given the broad product range affected, prioritize critical infrastructure and high-risk devices. 3) Network segmentation: Isolate vulnerable wireless devices and critical systems on segmented networks to limit the blast radius of potential DoS attacks. 4) Device hardening: Disable or restrict Wi-Fi features that are not in use, particularly those related to EHT operations, if configurable. 5) Incident response readiness: Prepare for potential transient connectivity disruptions by implementing failover mechanisms and maintaining communication alternatives. 6) Vendor engagement: Engage with device manufacturers and service providers to confirm patch availability and deployment timelines. 7) Awareness and training: Educate IT and security teams about the nature of this vulnerability and signs of exploitation attempts to enable rapid detection and response.

Description

Transient DOS while processing the EHT operation IE in the received beacon frame.

Impact

For European organizations, the impact of CVE-2025-21463 can be significant due to the widespread use of Qualcomm Snapdragon chipsets in mobile devices, IoT equipment, automotive systems, and enterprise wireless infrastructure. A successful exploitation could lead to transient denial of service conditions, disrupting wireless network availability. This can affect critical business operations relying on Wi-Fi connectivity, including remote work, cloud access, and IoT device communications. In sectors such as manufacturing, healthcare, automotive, and telecommunications, where Qualcomm platforms are embedded in operational technology and communication devices, service interruptions could lead to operational delays, safety risks, or degraded user experience. Although the vulnerability does not allow data leakage or code execution, repeated or targeted DoS attacks could be leveraged as part of broader multi-vector attacks, increasing the risk profile. The lack of required privileges or user interaction lowers the barrier for attackers, potentially enabling remote exploitation from within Wi-Fi range. Given the increasing reliance on wireless connectivity in European smart cities, industrial automation, and connected vehicles, this vulnerability poses a tangible risk to availability and operational continuity.

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