CVE-2024-53034: Qualcomm Snapdragon · Untrusted Pointer Dereference
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 17:16 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
- Monitor Qualcomm advisories closely and apply official patches immediately once released to remediate the vulnerability at the driver level.
- Until patches are available, restrict local access to devices with affected Snapdragon chipsets by enforcing strong endpoint security policies, including limiting administrative privileges and physical access controls.
- Employ mobile device management (MDM) solutions to enforce security configurations and detect anomalous behavior indicative of exploitation attempts.
- Use kernel integrity monitoring and endpoint detection and response (EDR) tools capable of identifying suspicious kernel-mode activities or memory corruption patterns.
- Educate users and administrators about the risks of installing untrusted applications or granting elevated permissions that could facilitate local exploitation.
- For organizations deploying IoT or embedded systems with these chipsets, implement network segmentation and strict firewall rules to limit exposure.
- Conduct regular security audits and penetration testing focusing on local privilege escalation vectors to identify potential exploitation paths.
- Collaborate with Qualcomm support channels for guidance and early access to patches or mitigations if available.
Description
Memory corruption occurs during an Escape call if an invalid Kernel Mode CPU event and sync object handle are passed with the DriverKnownEscape flag reset.