VulnerabilityPublished 3 Jun 2025

CVE-2024-53016: Qualcomm Snapdragon · Time-of-check Time-of-use (TOCTOU) Race Condition

Affects Qualcomm SnapdragonSource CVE Database V5

Not known to be exploited · CVSS 6.6 Medium.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score

6.6Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.07% 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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Jun 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-53016 effectively, European organizations should: 1) Monitor Qualcomm and device manufacturers for official patches or firmware updates addressing this TOCTOU race condition and apply them promptly once available. 2) Restrict local access to devices, enforcing strict endpoint security policies that limit installation of untrusted applications and prevent unauthorized physical access. 3) Employ mobile device management (MDM) solutions to control app permissions, especially those requesting camera or hardware-level access, reducing the attack surface for local exploitation. 4) Conduct security audits and penetration testing focusing on local privilege escalation vectors within devices using affected Snapdragon platforms. 5) For critical deployments, consider isolating or sandboxing camera driver processes where feasible to contain potential memory corruption impacts. 6) Educate users and administrators about the risks of installing unverified apps or connecting devices to untrusted networks that could facilitate local exploitation. 7) Collaborate with vendors to receive timely vulnerability intelligence and integrate detection mechanisms for anomalous camera driver behavior or memory corruption attempts. These steps go beyond generic patching advice by emphasizing access control, monitoring, and proactive security hygiene tailored to the nature of this local race condition vulnerability.

Description

Memory corruption while processing I2C settings in Camera driver.

Impact

For European organizations, the impact of CVE-2024-53016 can be significant, particularly for those relying on mobile devices, IoT wearables, or embedded systems powered by affected Qualcomm Snapdragon platforms. The vulnerability could be exploited by malicious local applications or attackers with physical or local access to the device to corrupt memory, potentially leading to privilege escalation or unauthorized manipulation of camera functions. This could compromise device integrity, leak sensitive information, or disrupt availability of camera-related services. Organizations in sectors such as telecommunications, mobile device manufacturing, healthcare (using wearable devices), and critical infrastructure that utilize Snapdragon-based hardware may face increased risk. The medium severity rating suggests that while remote exploitation is unlikely, insider threats or malicious apps could leverage this flaw to gain elevated privileges or disrupt device operations. The confidentiality impact is limited, but integrity and availability impacts are more pronounced, which could affect trustworthiness of devices used in secure communications or data capture. Given the widespread use of Snapdragon chips in consumer and enterprise mobile devices across Europe, this vulnerability could have broad implications if exploited in targeted attacks or supply chain compromises.

CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
Implementation
The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.
Implementation
When the file being altered is owned by the current user and group, set the effective gid and uid to that of the current user and group when executing this statement.
Architecture and Design
Limit the interleaving of operations on files from multiple processes.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.3 (opens in a new tab)
V11.1.6 (opens in a new tab)
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Race Conditions via Symbolic Links (opens in a new tab)
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

docs.qualcomm.com/product/publicresources/securitybulletin/june-2025-bulletin.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Jul 2025, 18:27 UTC

WeaknessesCWE-367

Technical details

References

Community reviews

Related threats