Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-53034 is a high-severity Untrusted Pointer Dereference (CWE-822) vulnerability in Qualcomm Fastconnect 6900 Firmware. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-53034 is a memory corruption vulnerability that occurs during an Escape call when an invalid Kernel Mode CPU event and sync object handle are passed with the DriverKnownEscape flag reset. It affects Qualcomm software components, as documented in the vendor's security bulletin. The issue is associated with CWE-822 (Untrusted Pointer Dereference) and CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), and it received a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), indicating high severity.
A local attacker with low privileges can exploit this vulnerability with low attack complexity and no user interaction required. Exploitation triggers memory corruption, potentially enabling high-impact outcomes such as unauthorized data access, modification of system integrity, or denial of service through kernel instability.
Qualcomm's March 2025 security bulletin (https://docs.qualcomm.com/product/publicresources/securitybulletin/march-2025-bulletin.html) addresses the vulnerability, providing guidance on affected products and available patches for mitigation. Security practitioners should review the bulletin for specific remediation steps tailored to deployed Qualcomm platforms.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-5778
Vulnerability Data
Memory corruption occurs during an Escape call if an invalid Kernel Mode CPU event and sync object handle are passed with the DriverKnownEscape flag reset.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V17.3.2
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover instances where untrusted data is turned into a pointer and dereferenced.
Validating all information inputs stops untrusted values from being accepted and converted into dereferenceable pointers.
Secure engineering principles require memory-safe design and coding that structurally avoids buffer-boundary violations.
Memory-protection mechanisms limit the damage from an invalid pointer dereference without stopping the root coding flaw.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent introduction of untrusted pointer handling during development.
Runtime monitoring of software and data can detect adverse events resulting from exploitation of the weakness.
Vulnerability identification processes can discover instances of this weakness via code review or scanning.
Receiving and triaging vulnerability disclosures commonly includes buffer-related reports.
Developer training on secure coding reduces introduction of memory-buffer errors.
Patching replaces vulnerable code containing buffer-boundary defects.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect pointer-dereference flaws before release.
Secure development lifecycle includes pointer-safety practices that reduce untrusted pointer dereference risk.
Application security requirements can mandate validation of pointers obtained from untrusted sources.
Secure architecture principles discourage direct use of untrusted values as pointers.
Secure coding standards explicitly forbid dereferencing pointers derived from untrusted input.