CVE-2024-45580: Qualcomm Snapdragon · Use After Free
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 14:05 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 3 Mar 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
- Restrict access to IOCTL interfaces: Limit which users and applications can invoke IOCTL calls on affected devices by enforcing strict access controls and permissions.
- Employ privilege separation: Ensure that untrusted or less-privileged applications cannot directly interact with kernel drivers handling IOCTL calls.
- Use runtime memory protection: Enable and enforce kernel-level memory protection mechanisms such as Kernel Address Space Layout Randomization (KASLR), Supervisor Mode Access Prevention (SMAP), and Supervisor Mode Execution Prevention (SMEP) to mitigate exploitation impact.
- Monitor device behavior: Deploy endpoint detection and response (EDR) tools to detect anomalous behavior indicative of exploitation attempts, such as unusual IOCTL call patterns or memory corruption symptoms.
- Apply vendor patches promptly: Monitor Qualcomm and device OEM advisories for patches addressing CVE-2024-45580 and deploy them as soon as they become available.
- Limit installation of untrusted applications: Enforce application whitelisting and restrict installation of apps from unknown sources to reduce the risk of local privilege escalation.
- Conduct regular security audits: Review device configurations and kernel driver interfaces for potential misuse or vulnerabilities.
- For enterprise deployments, consider network segmentation and device management policies to isolate vulnerable devices until patched.
Description
Memory corruption while handling multuple IOCTL calls from userspace for remote invocation.