Skip to main content
VulnerabilityPublished

CVE-2024-53013: Qualcomm Snapdragon · Classic Buffer Overflow

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 6.6 Medium.

Data as of 26 Oct 2026, 10:12 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-53013, European organizations should: 1) Monitor Qualcomm and device vendors for official patches or firmware updates addressing this vulnerability and prioritize timely deployment across all affected devices. 2) Implement strict application whitelisting and privilege management on devices to limit the ability of untrusted or low-privilege applications to interact with voice call registration components. 3) Employ endpoint detection and response (EDR) solutions capable of detecting anomalous behavior indicative of memory corruption or privilege escalation attempts on mobile and embedded devices. 4) Restrict local access to devices, enforcing strong physical security and user authentication to reduce the risk of local exploitation. 5) For organizations deploying IoT or automotive systems with affected chipsets, conduct thorough security assessments and consider network segmentation to isolate vulnerable devices from critical infrastructure. 6) Educate users and administrators about the risks of installing untrusted applications and the importance of applying security updates promptly. 7) Collaborate with device manufacturers and suppliers to verify the vulnerability status of deployed hardware and request security advisories or mitigations specific to their device models. These measures go beyond generic patching by emphasizing access control, monitoring, and supply chain engagement to reduce exploitation likelihood.

Description

Memory corruption may occur while processing voice call registration with user.

References

Community reviews

Loading reviews…