Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-45565: CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition in Qualcomm, Inc. Snapdragon

0
High
VulnerabilityCVE-2024-45565cvecve-2024-45565cwe-367
Published: Tue May 06 2025 (05/06/2025, 08:31:58 UTC)
Source: CVE
Vendor/Project: Qualcomm, Inc.
Product: Snapdragon

Description

Memory corruption when blob structure is modified by user-space after kernel verification.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 20:20:44 UTC

Technical Analysis

CVE-2024-45565 is a time-of-check to time-of-use (TOCTOU) race condition vulnerability classified under CWE-367, affecting Qualcomm Snapdragon platforms such as SDM429W, Snapdragon 429 Mobile Platform, WCN3620, and WCN3660B. The vulnerability occurs when a blob structure is verified by the kernel but is subsequently modified by user-space before the kernel uses it, leading to memory corruption. This race condition allows an attacker with low-level privileges to manipulate data after kernel verification but before use, potentially causing arbitrary code execution, privilege escalation, or denial of service. The vulnerability has a CVSS v3.1 score of 7.8, reflecting high impact on confidentiality, integrity, and availability, with low attack complexity and requiring only low privileges and no user interaction. The affected Snapdragon platforms are widely used in mobile devices and embedded systems, making this a significant threat vector. No patches are currently linked, and no known exploits have been reported in the wild, but the potential impact warrants urgent attention. The vulnerability highlights the critical need for proper synchronization and validation mechanisms between kernel and user-space interactions to prevent race conditions that lead to memory corruption.

Potential Impact

The exploitation of CVE-2024-45565 can lead to severe consequences including full compromise of device confidentiality, integrity, and availability. Attackers with low privilege local access can exploit the race condition to execute arbitrary code in kernel context, escalate privileges, or cause system crashes and denial of service. This can result in unauthorized data access, persistent malware installation, or disruption of critical services on affected devices. Given the widespread use of Qualcomm Snapdragon platforms in smartphones, IoT devices, and embedded systems, the vulnerability poses a significant risk to consumer privacy, enterprise security, and critical infrastructure relying on these devices. Organizations deploying affected hardware in sensitive environments such as telecommunications, healthcare, and industrial control systems may face increased risk of targeted attacks or supply chain compromises. The absence of known exploits in the wild currently reduces immediate risk but does not diminish the urgency for remediation due to the vulnerability’s high severity and ease of exploitation.

Mitigation Recommendations

To mitigate CVE-2024-45565, organizations should: 1) Monitor Qualcomm and device vendors for official patches and apply them promptly once available. 2) Implement strict synchronization mechanisms in kernel code to ensure that user-space data structures cannot be modified after kernel verification and before use, effectively eliminating the TOCTOU window. 3) Employ runtime integrity checks and memory protection features such as Kernel Address Space Layout Randomization (KASLR) and Supervisor Mode Access Prevention (SMAP) to reduce exploitation success. 4) Restrict local access to devices by enforcing least privilege principles and limiting untrusted user-space code execution. 5) Conduct thorough code audits and fuzz testing on kernel interfaces interacting with user-space to detect similar race conditions. 6) For critical deployments, consider additional monitoring for anomalous kernel behavior or memory corruption indicators that could signal exploitation attempts. 7) Educate developers on secure coding practices to avoid TOCTOU vulnerabilities in future kernel and driver development. These steps collectively reduce the risk of exploitation and enhance overall device security posture.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
qualcomm
Date Reserved
2024-09-02T10:26:15.224Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682d981bc4522896dcbd9c44

Added to database: 5/21/2025, 9:08:43 AM

Last enriched: 2/26/2026, 8:20:44 PM

Last updated: 3/25/2026, 8:21:20 AM

Views: 52

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses