CVE-2025-21441: Qualcomm Snapdragon · Out-of-bounds Write
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation 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 26 Oct 2026.
What to do
AI-suggested
Organizations should implement the following specific mitigations: 1) Restrict local access to devices with affected Qualcomm components by enforcing strict user privilege separation and limiting access to trusted users only. 2) Monitor and control IOCTL calls and other driver interactions through endpoint protection platforms capable of detecting anomalous behavior targeting WLAN drivers. 3) Employ application whitelisting and behavior-based detection to identify attempts to exploit the vulnerability. 4) Maintain up-to-date device firmware and operating system patches, and prioritize deployment of Qualcomm-issued security updates once available. 5) For enterprise-managed devices, consider disabling or restricting WLAN driver features that accept user-space board data writes if feasible. 6) Conduct regular security audits and penetration testing focusing on local privilege escalation vectors. 7) Educate users about the risks of installing untrusted software or granting unnecessary local access, as exploitation requires local presence. These targeted actions go beyond generic patching advice and help reduce the attack surface until official patches are released.
Description
Memory corruption when IOCTL call is invoked from user-space to write board data to WLAN driver.