VulnerabilityPublished 24 Sep 2025Updated 25 Sep 2025

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

Affects Qualcomm SnapdragonSource CVE Database V5

Not known to be exploited · CVSS 8.2 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

8.2High

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:H/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: Low

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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Sep 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. Immediate inventory and identification of all devices and systems using affected Qualcomm Snapdragon platforms within the organization, including mobile devices, IoT endpoints, automotive systems, and wireless modules. 2. Monitor Qualcomm's official security advisories and vendor updates for patches or firmware updates addressing CVE-2025-21484. Deploy patches promptly once available. 3. Employ network-level protections such as RTP packet filtering, anomaly detection, and intrusion prevention systems to detect and block malformed or suspicious RTP traffic that could exploit the vulnerability. 4. For enterprise mobile device management (MDM), enforce strict update policies and restrict installation of untrusted applications that might facilitate exploitation. 5. Implement network segmentation and zero-trust principles to limit exposure of vulnerable devices to untrusted networks or external attackers. 6. Conduct security awareness training for staff to recognize potential signs of exploitation or unusual device behavior. 7. Collaborate with device manufacturers and service providers to ensure timely updates and coordinated vulnerability response. 8. Consider deploying endpoint detection and response (EDR) tools capable of identifying anomalous memory access patterns or RTP stream manipulations. 9. For critical infrastructure and automotive deployments, perform rigorous security testing and validation of firmware updates to prevent exploitation. These measures go beyond generic advice by focusing on proactive identification, network-level controls specific to RTP traffic, and coordination with vendors for patch management.

Description

Information disclosure when UE receives the RTP packet from the network, while decoding and reassembling the fragments from RTP packet.

Impact

For European organizations, the impact of CVE-2025-21484 is substantial due to the widespread use of Qualcomm Snapdragon chipsets in smartphones, tablets, IoT devices, automotive systems, and wearable technology. Confidentiality is the primary concern, as the buffer over-read can lead to unauthorized disclosure of sensitive information residing in memory, potentially including cryptographic keys, user data, or other protected information. This could facilitate further targeted attacks, espionage, or data leakage. The vulnerability does not directly affect integrity but has a low impact on availability, meaning devices may experience minor disruptions but are unlikely to be rendered inoperable. European enterprises relying on mobile communications for critical operations, remote work, or secure communications could face increased risks of data breaches or interception. Additionally, sectors such as automotive, healthcare, and industrial IoT that integrate Snapdragon platforms may be exposed to information leakage, raising compliance and safety concerns. The lack of required privileges or user interaction for exploitation increases the threat level, as attackers can remotely target vulnerable devices over the network. Although no exploits are currently known in the wild, the high CVSS score and broad product impact necessitate urgent attention from European organizations to assess and mitigate risks.

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 2 Oct 2025, 01:05 UTC

WeaknessesCWE-126

Technical details

References

Community reviews

Related threats