Skip to main content
VulnerabilityPublished Updated

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

Affects Qualcomm SnapdragonSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High.

Data as of 9 Nov 2026, 23:23 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 19% 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 9 Nov 2026.

What to do

AI-suggested

  1. Immediate mitigation involves network-level filtering to detect and block suspicious RTP packets with anomalous padding bits, potentially using deep packet inspection tools to identify malformed RTP streams.
  2. Organizations should monitor network traffic for unusual RTP activity and implement anomaly detection to flag potential exploitation attempts.
  3. Device owners should apply firmware and software updates from Qualcomm or device manufacturers as soon as patches become available.
  4. For critical environments, consider isolating vulnerable devices from untrusted networks or restricting RTP traffic to trusted sources only.
  5. Employ endpoint security solutions capable of detecting abnormal memory access patterns or unusual RTP packet processing behaviors.
  6. Engage with device vendors and mobile operators to confirm patch availability timelines and coordinate timely deployment.
  7. For automotive and IoT deployments, implement layered security controls including network segmentation and secure update mechanisms to reduce exposure.
  8. Educate users and administrators about the risks of RTP-based attacks and encourage vigilance for suspicious device behavior or network anomalies. These targeted measures go beyond generic advice by focusing on RTP traffic characteristics, device-specific patching, and network monitoring tailored to the nature of this vulnerability.

Description

Information disclosure while decoding this RTP packet headers received by UE from the network when the padding bit is set.

References

Community reviews

Loading reviews…