CVE-2024-45557: Qualcomm Snapdragon · Use of Out-of-range Pointer Offset
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 06:26 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 2026-10-26.
What to do
AI-suggested
To mitigate CVE-2024-45557, organizations and device manufacturers should: 1) Monitor Qualcomm and device vendor advisories closely for official patches and firmware updates addressing this vulnerability and apply them promptly once available. 2) Implement strict application sandboxing and privilege separation to reduce the risk of local privilege escalation by untrusted applications. 3) Employ runtime protections such as memory integrity checks and exploit mitigation techniques (e.g., Control Flow Integrity, Address Space Layout Randomization) where supported by the platform. 4) Limit installation of untrusted or unnecessary applications to reduce attack surface. 5) For enterprise-managed devices, enforce mobile device management (MDM) policies that restrict local access and privilege escalation attempts. 6) Conduct regular security audits and penetration testing focused on local privilege escalation vectors. 7) Educate users about the risks of installing unverified apps and the importance of timely updates. These steps, combined with vendor patches, will help reduce the risk posed by this vulnerability.
Description
Memory corruption can occur when TME processes addresses from TZ and MPSS requests without proper validation.