Skip to main content
CVE-2024-21476VulnerabilityPublished Updated

CVE-2024-21476: Qualcomm Snapdragon · Improper Input Validation

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 06:26 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 6 May 2024

  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 2026-10-26.

What to do

AI-suggested

European organizations should implement a multi-layered mitigation strategy: 1) Monitor vendor communications closely for Qualcomm patches or firmware updates addressing CVE-2024-21476 and prioritize their deployment across all affected devices. 2) Restrict local access to devices with vulnerable Snapdragon components by enforcing strong physical security controls and endpoint access policies. 3) Employ endpoint detection and response (EDR) solutions to identify anomalous local activity that could indicate exploitation attempts. 4) Harden device configurations by disabling unnecessary services and interfaces that could provide local access vectors. 5) Educate users and administrators about the risks of local privilege escalation vulnerabilities and the importance of reporting suspicious behavior. 6) For organizations deploying IoT or embedded devices with affected chipsets, implement network segmentation to limit potential lateral movement from compromised devices. 7) Collaborate with device manufacturers and service providers to ensure timely updates and coordinated vulnerability disclosure. 8) Conduct regular security audits and penetration testing focusing on local access controls and input validation weaknesses in device firmware. These steps go beyond generic patching advice by emphasizing access control, monitoring, and supply chain coordination tailored to the Snapdragon ecosystem.

Description

Memory corruption when the channel ID passed by user is not validated and further used.

References

Community reviews

Loading reviews…