Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-47405 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 0.1th 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-2025-47405 is a memory corruption vulnerability, classified as CWE-822 (Untrusted Pointer Dereference), that occurs when processing camera sensor input/output control codes with invalid output buffers. It affects components within Qualcomm products, as documented in the vendor's May 2026 security bulletin. The vulnerability carries 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 with significant potential impacts.
A local attacker with low privileges can exploit this vulnerability through low-complexity means without requiring user interaction. Exploitation involves supplying malformed camera sensor IOCTL requests with invalid output buffers, leading to memory corruption. Successful attacks could grant high-level impacts on confidentiality, integrity, and availability, such as arbitrary code execution in the context of the affected process or complete system denial of service.
Qualcomm's May 2026 security bulletin at https://docs.qualcomm.com/product/publicresources/securitybulletin/may-2026-bulletin.html provides details on affected products, patch availability, and recommended mitigations for this CVE. Security practitioners should consult the bulletin for version-specific remediation steps.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-209630
Vulnerability Data
Memory corruption when processing camera sensor input/output control codes with invalid output buffers.
- 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.