Skip to main content
VulnerabilityPublished

CVE-2024-53017: Qualcomm Snapdragon · Use of Out-of-range Pointer Offset

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 6.6 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
6.6Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.09% chance of exploitation in 30 days – higher than 0% 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:L/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jun 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

To mitigate CVE-2024-53017, organizations should: 1) Monitor Qualcomm and device vendors for official patches or firmware updates addressing this vulnerability and apply them promptly. 2) Restrict local access to devices running affected Snapdragon platforms, enforcing strict device usage policies and limiting physical or local network access to trusted personnel only. 3) Employ mobile device management (MDM) solutions to enforce security policies, detect anomalous behavior, and control application installations to reduce the risk of local privilege escalation. 4) Conduct regular security audits and vulnerability assessments on embedded and mobile devices to identify outdated firmware or unpatched vulnerabilities. 5) For critical embedded systems, consider network segmentation and additional monitoring to detect exploitation attempts. 6) Educate users about the risks of installing untrusted applications or granting unnecessary permissions that could facilitate local exploitation. 7) Implement runtime protections such as memory protection mechanisms and integrity checks where possible to reduce the impact of memory corruption vulnerabilities.

Description

Memory corruption while handling test pattern generator IOCTL command.

References

Community reviews

Loading reviews…