Skip to main content
VulnerabilityPublished Updated

CVE-2024-53024: Qualcomm Snapdragon · NULL Pointer Dereference

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Mar 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-53024, organizations and device manufacturers should prioritize the following actions: 1) Apply official patches and firmware updates from Qualcomm and device vendors as soon as they become available to address the NULL pointer dereference in the display driver. 2) Implement strict access controls and privilege separation to limit local user capabilities, reducing the risk of exploitation by low-privilege attackers. 3) Employ runtime memory protection mechanisms such as Address Space Layout Randomization (ASLR) and Control Flow Integrity (CFI) to hinder exploitation of memory corruption vulnerabilities. 4) Monitor system logs and device detach events for anomalies that may indicate exploitation attempts or driver malfunctions. 5) For enterprise-managed devices, restrict installation of untrusted applications and enforce application whitelisting to minimize the attack surface. 6) Conduct regular security assessments and penetration testing focusing on device drivers and hardware interfaces. 7) Educate users and administrators about the risks of local privilege escalation vulnerabilities and the importance of timely updates. These targeted measures go beyond generic advice by focusing on the unique aspects of device driver vulnerabilities and the Snapdragon ecosystem.

Description

Memory corruption in display driver while detaching a device.

References

Community reviews

Loading reviews…