Skip to main content
VulnerabilityPublished Updated

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

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 10:12 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Apr 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

AI-suggested

  1. Apply official firmware and software updates from Qualcomm and device manufacturers as soon as they become available to patch the vulnerability.
  2. Network operators should monitor Wi-Fi management frames, specifically ADD TS requests, for anomalous or malformed packets that could indicate exploitation attempts.
  3. Implement network segmentation to isolate vulnerable wireless devices from critical infrastructure to limit potential impact.
  4. Disable or restrict WMM features on access points and devices where QoS is not essential, reducing the attack surface related to TSpec session establishment.
  5. Employ intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics targeting malformed ADD TS requests.
  6. For automotive and IoT deployments, coordinate with vendors to ensure timely updates and consider fallback operational modes that reduce reliance on vulnerable wireless features.
  7. Educate security teams and end users about the risk and signs of device instability that may indicate exploitation attempts.
  8. Maintain an inventory of affected devices to prioritize patching and monitoring efforts effectively.

Description

Memory corruption occurs while connecting a STA to an AP and initiating an ADD TS request from the AP to establish a TSpec session.

References

Community reviews

Loading reviews…